Merge branch 'master' of https://github.com/portainer/portainer-docs
keverv
commit
99ad5d2e4b
|
|
@ -43,9 +43,9 @@ volumes:
|
|||
|
||||
To setup and start working with this recipe, you need to change the VIRTUAL_HOST value. You can then run the following:
|
||||
|
||||
<pre><code>$ docker-compose up -d</code></pre>
|
||||
<pre><code>docker-compose up -d</code></pre>
|
||||
|
||||
Once complete, you will able to run <code>$ docker ps</code> and you will see an output similar to this:
|
||||
Once complete, you will able to run <code> docker ps</code> and you will see an output similar to this:
|
||||
|
||||
<pre><code>CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
|
||||
088da047e931 portainer/portainer-ce:2.0.0 "/portainer -H unix:…" 32 minutes ago Up 22 minutes 0.0.0.0:8000->8000/tcp, 9000/tcp nginx-port_portainer_1
|
||||
|
|
@ -63,13 +63,13 @@ Before deploying, you need to create 2 elements: Networks and volumes.
|
|||
|
||||
1. First, create 2 networks for the agent to communicate with Portainer Server and other to "expose" the Portainer container to the same network that as the Reverse Proxy
|
||||
|
||||
<pre><code>$ docker network create -d overlay proxy</code></pre>
|
||||
<pre><code> docker network create -d overlay proxy</code></pre>
|
||||
|
||||
<pre><code>$ docker network create -d agent_network</code></pre>
|
||||
<pre><code> docker network create -d agent_network</code></pre>
|
||||
|
||||
2. Then create the volume:
|
||||
|
||||
<pre><code>$ docker volume create portainer_data</code></pre>
|
||||
<pre><code> docker volume create portainer_data</code></pre>
|
||||
|
||||
3. Save the below recipe as portainer.yml
|
||||
|
||||
|
|
@ -137,9 +137,9 @@ volumes:
|
|||
|
||||
5. You're now ready to deploy Portainer by executing the following:
|
||||
|
||||
<pre><code>$ docker stack deploy portainer -c portainer.yml</code></pre>
|
||||
<pre><code> docker stack deploy portainer -c portainer.yml</code></pre>
|
||||
|
||||
6. To check the deployment you can run <code>$ docker service ls</code> and you will see an output similar to the following:
|
||||
6. To check the deployment you can run <code> docker service ls</code> and you will see an output similar to the following:
|
||||
|
||||
<pre><code>ID NAME MODE REPLICAS IMAGE PORTS
|
||||
gy2bjxid0g4p portainer_agent global 1/1 portainer/agent:latest
|
||||
|
|
|
|||
|
|
@ -94,13 +94,13 @@ Before deploying, you need to create 2 elements: Networks and volumes.
|
|||
|
||||
1. First, create 2 overlay networks:
|
||||
|
||||
<pre><code>$ docker network create -d overlay agent_network</code></pre>
|
||||
<pre><code> docker network create -d overlay agent_network</code></pre>
|
||||
|
||||
<pre><code>$ docker network create -d overlay public</code></pre>
|
||||
<pre><code> docker network create -d overlay public</code></pre>
|
||||
|
||||
2. Then create the volume:
|
||||
|
||||
<pre><code>$ docker volume create portainer_data</code></pre>
|
||||
<pre><code> docker volume create portainer_data</code></pre>
|
||||
|
||||
3. Save the below recipe as portainer.yml
|
||||
|
||||
|
|
@ -187,9 +187,9 @@ volumes:
|
|||
|
||||
5. You're now ready to deploy Portainer by executing the following:
|
||||
|
||||
<pre><code>$ docker stack deploy portainer -c portainer.yml</code></pre>
|
||||
<pre><code> docker stack deploy portainer -c portainer.yml</code></pre>
|
||||
|
||||
6. To check the deployment you can run <code>$ docker service ls</code> and you will see an output similar to the following:
|
||||
6. To check the deployment you can run <code> docker service ls</code> and you will see an output similar to the following:
|
||||
|
||||
<pre><code>ID NAME MODE REPLICAS IMAGE PORTS
|
||||
lt21zrypsll6 portainer_agent global 1/1 portainer/agent:latest
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ Portainer allows you to specify a bcrypt encrypted password from the command lin
|
|||
|
||||
You can generate the encrypted password with the following command if you have installed apache2-utils package:
|
||||
|
||||
<pre><code>$ htpasswd -nb -B admin "your-password" | cut -d ":" -f 2</code></pre>
|
||||
<pre><code> htpasswd -nb -B admin "your-password" | cut -d ":" -f 2</code></pre>
|
||||
|
||||
If your system does not have the mentioned command, you can run a container to run the command:
|
||||
|
||||
|
|
@ -23,17 +23,17 @@ You can also store the plaintext password inside a file and use the <code>--admi
|
|||
|
||||
Add your password to a file running the following command:
|
||||
|
||||
<pre><code>$ echo -n mypassword > /tmp/portainer_password</code></pre>
|
||||
<pre><code> echo -n mypassword > /tmp/portainer_password</code></pre>
|
||||
|
||||
Now you can start the Portainer container by running:
|
||||
|
||||
<pre><code>$ docker run -d -p 9000:9000 -p 8000:8000 -v /var/run/docker.sock:/var/run/docker.sock -v /tmp/portainer_password:/tmp/portainer_password portainer/portainer-ce --admin-password-file /tmp/portainer_password</code></pre>
|
||||
<pre><code> docker run -d -p 9000:9000 -p 8000:8000 -v /var/run/docker.sock:/var/run/docker.sock -v /tmp/portainer_password:/tmp/portainer_password portainer/portainer-ce --admin-password-file /tmp/portainer_password</code></pre>
|
||||
|
||||
This works well with Docker Swarm and Docker secrets too:
|
||||
|
||||
<pre><code>$ echo -n mypassword | docker secret create portainer-pass -</code></pre>
|
||||
<pre><code> echo -n mypassword | docker secret create portainer-pass -</code></pre>
|
||||
|
||||
<pre><code>$ docker service create \
|
||||
<pre><code> docker service create \
|
||||
--name portainer \
|
||||
--secret portainer-pass \
|
||||
--publish 9000:9000 \
|
||||
|
|
@ -53,21 +53,21 @@ Portainer allows you to hide containers with a specific label by using the -l fl
|
|||
|
||||
For example, take a container started with the label owner=acme (note that this is an example label, you can define your own labels):
|
||||
|
||||
<pre><code>$ docker run -d --label owner=acme nginx</code></pre>
|
||||
<pre><code> docker run -d --label owner=acme nginx</code></pre>
|
||||
|
||||
To hide this container, simply add the -l owner=acme option on the CLI when starting Portainer:
|
||||
|
||||
<pre><code>$ docker run -d -p 9000:9000 -p 8000:8000 -v /var/run/docker.sock:/var/run/docker.sock portainer/portainer-ce -l owner=acme</code></pre>
|
||||
<pre><code> docker run -d -p 9000:9000 -p 8000:8000 -v /var/run/docker.sock:/var/run/docker.sock portainer/portainer-ce -l owner=acme</code></pre>
|
||||
|
||||
Note that the -l flag can be repeated multiple times to specify multiple labels:
|
||||
|
||||
<pre><code>$ docker run -d -p 9000:9000 -p 8000:8000 -v /var/run/docker.sock:/var/run/docker.sock portainer/portainer-ce -l owner=acme -l service=secret</code></pre>
|
||||
<pre><code> docker run -d -p 9000:9000 -p 8000:8000 -v /var/run/docker.sock:/var/run/docker.sock portainer/portainer-ce -l owner=acme -l service=secret</code></pre>
|
||||
|
||||
## Use your own logo
|
||||
|
||||
You do not like our logo? Want to make Portainer more corporate? Don’t worry, you can easily switch for an external logo (it must be exactly 155px by 55px) using the <code>--logo flag</code>:
|
||||
|
||||
<pre><code>$ docker run -d -p 9000:9000 -p 8000:8000 -v /var/run/docker.sock:/var/run/docker.sock portainer/portainer-ce --logo "https://www.docker.com/sites/all/themes/docker/assets/images/brand-full.svg"</code></pre>
|
||||
<pre><code> docker run -d -p 9000:9000 -p 8000:8000 -v /var/run/docker.sock:/var/run/docker.sock portainer/portainer-ce --logo "https://www.docker.com/sites/all/themes/docker/assets/images/brand-full.svg"</code></pre>
|
||||
This can also be completed via the GUI in the Portaner Settings menu
|
||||
|
||||
## Use your own templates
|
||||
|
|
@ -80,7 +80,7 @@ Note: at the moment, templates are only loaded once at first Portainer startup.
|
|||
|
||||
Using the <code>--templates</code> flag you can specify an URL where the template file can be accessed via HTTP.
|
||||
|
||||
<pre><code>$ docker run -d -p 9000:9000 -p 8000:8000 -v /var/run/docker.sock:/var/run/docker.sock portainer/portainer-ce --templates http://my-host.my-domain/templates.json</code></pre>
|
||||
<pre><code> docker run -d -p 9000:9000 -p 8000:8000 -v /var/run/docker.sock:/var/run/docker.sock portainer/portainer-ce --templates http://my-host.my-domain/templates.json</code></pre>
|
||||
|
||||
Suggestion: You can host your template files in [Github](https://www.github.com)
|
||||
|
||||
|
|
|
|||
|
|
@ -19,7 +19,7 @@ and looking for a storage class with (default) after its name:
|
|||
|
||||
If you want to make a storage class the default, you can type the command:
|
||||
|
||||
<pre><code> > kubectl patch storageclass <storage-class-name> -p '{"metadata": {"annotations":{"storageclass.kubernetes.io/is-default-class":"true"}}}' </code></pre>
|
||||
<pre><code> >kubectl patch storageclass <storage-class-name> -p '{"metadata": {"annotations":{"storageclass.kubernetes.io/is-default-class":"true"}}}' </code></pre>
|
||||
|
||||
and replace <storage-class-name> with the name of your storage class (eg: kubectl patch storageclass local-path -p '{"metadata": {"annotations":{"storageclass.kubernetes.io/is-default-class":"true"}}}'
|
||||
|
||||
|
|
@ -30,40 +30,40 @@ Alternatively, if you are using HELM you can use:
|
|||
|
||||
First, add the Portainer helm repo running the following:
|
||||
|
||||
<pre><code>$ helm repo add portainer https://portainer.github.io/k8s/</code></pre>
|
||||
<pre><code>$ helm repo update</code></pre>
|
||||
<pre><code> helm repo add portainer https://portainer.github.io/k8s/</code></pre>
|
||||
<pre><code> helm repo update</code></pre>
|
||||
|
||||
Then, create the Portainer namespace in your cluster
|
||||
|
||||
<pre><code>$ kubectl create namespace portainer</code></pre>
|
||||
<pre><code> kubectl create namespace portainer</code></pre>
|
||||
|
||||
#### For NodePort
|
||||
|
||||
Using the following command, Portainer will run in the port 30777
|
||||
|
||||
<pre><code>$ helm install -n portainer portainer portainer/portainer</code></pre>
|
||||
<pre><code> helm install -n portainer portainer portainer/portainer</code></pre>
|
||||
|
||||
#### For Load Balancer
|
||||
|
||||
Using the following command, Portainer will run in the port 9000.
|
||||
|
||||
<pre><code>$ helm install -n portainer portainer portainer/portainer --set service.type=LoadBalancer</code></pre>
|
||||
<pre><code> helm install -n portainer portainer portainer/portainer --set service.type=LoadBalancer</code></pre>
|
||||
|
||||
#### For Ingress
|
||||
|
||||
<pre><code>$ helm install -n portainer portainer portainer/portainer --set service.type=ClusterIP</code></pre>
|
||||
<pre><code> helm install -n portainer portainer portainer/portainer --set service.type=ClusterIP</code></pre>
|
||||
|
||||
### Using YAML Manifest
|
||||
|
||||
First create the Portainer namespace in your cluster
|
||||
|
||||
<pre><code>$ kubectl create namespace portainer</code></pre>
|
||||
<pre><code> kubectl create namespace portainer</code></pre>
|
||||
|
||||
#### For NodePort
|
||||
|
||||
Using the following command, Portainer will run in the port 30777
|
||||
|
||||
<pre><code>$ kubectl apply -n portainer -f https://raw.githubusercontent.com/portainer/k8s/master/deploy/manifests/portainer/portainer.yaml</code></pre>
|
||||
<pre><code> kubectl apply -n portainer -f https://raw.githubusercontent.com/portainer/k8s/master/deploy/manifests/portainer/portainer.yaml</code></pre>
|
||||
|
||||
#### For Load Balancer
|
||||
|
||||
|
|
@ -81,16 +81,16 @@ To see the requeriments, please, visit the page of [requirements](/v2.0/deploy/r
|
|||
|
||||
Use the following Docker commands to deploy the Portainer Server; note the agent is not needed on standalone hosts, however it does provide additional functionality if used (see portainer and agent scenario below):
|
||||
|
||||
<pre><code>$ docker volume create portainer_data</code></pre>
|
||||
<pre><code> docker volume create portainer_data</code></pre>
|
||||
|
||||
<pre><code>$ docker run -d -p 8000:8000 -p 9000:9000 --name=portainer --restart=always -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer-ce</code></pre>
|
||||
<pre><code> docker run -d -p 8000:8000 -p 9000:9000 --name=portainer --restart=always -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer-ce</code></pre>
|
||||
|
||||
### Docker Swarm
|
||||
|
||||
Deploying Portainer and the Portainer Agent to manage a Swarm cluster is easy! You can directly deploy Portainer as a service in your Docker cluster. Note that this method will automatically deploy a single instance of the Portainer Server, and deploy the Portainer Agent as a global service on every node in your cluster.
|
||||
|
||||
<pre><code>$ curl -L https://downloads.portainer.io/portainer-agent-stack.yml -o portainer-agent-stack.yml</code></pre>
|
||||
<pre><code>$ docker stack deploy -c portainer-agent-stack.yml portainer</code></pre>
|
||||
<pre><code> curl -L https://downloads.portainer.io/portainer-agent-stack.yml -o portainer-agent-stack.yml</code></pre>
|
||||
<pre><code> docker stack deploy -c portainer-agent-stack.yml portainer</code></pre>
|
||||
|
||||
## Portainer Agent Deployments Only
|
||||
|
||||
|
|
@ -102,7 +102,7 @@ Run the following command to deploy the Agent in your Docker host.
|
|||
### Docker Swarm
|
||||
Deploy Portainer Agent on a remote LINUX Swarm Cluster as a Swarm Service, run this command on a manager node in the remote cluster.
|
||||
|
||||
<pre><code>$ docker service create --name portainer_agent --network portainer_agent_network --publish mode=host,target=9001,published=9001 -e AGENT_CLUSTER_ADDR=tasks.portainer_agent --mode global --mount type=bind,src=//var/run/docker.sock,dst=/var/run/docker.sock --mount type=bind,src=//var/lib/docker/volumes,dst=/var/lib/docker/volumes –-mount type=bind,src=/,dst=/host portainer/agent</code></pre>
|
||||
<pre><code> docker service create --name portainer_agent --network portainer_agent_network --publish mode=host,target=9001,published=9001 -e AGENT_CLUSTER_ADDR=tasks.portainer_agent --mode global --mount type=bind,src=//var/run/docker.sock,dst=/var/run/docker.sock --mount type=bind,src=//var/lib/docker/volumes,dst=/var/lib/docker/volumes –-mount type=bind,src=/,dst=/host portainer/agent</code></pre>
|
||||
|
||||
## Notes
|
||||
|
||||
|
|
|
|||
|
|
@ -26,10 +26,10 @@ After a few minutes, you will see that Kubernetes is running:
|
|||
|
||||
First create the Portainer namespace in your cluster
|
||||
|
||||
<pre><code>$ kubectl create namespace portainer</code></pre>
|
||||
<pre><code> kubectl create namespace portainer</code></pre>
|
||||
|
||||
#### For NodePort
|
||||
<pre><code>$ kubectl apply -n portainer -f https://raw.githubusercontent.com/portainer/k8s/master/deploy/manifests/portainer/portainer.yaml</code></pre>
|
||||
<pre><code> kubectl apply -n portainer -f https://raw.githubusercontent.com/portainer/k8s/master/deploy/manifests/portainer/portainer.yaml</code></pre>
|
||||
|
||||
If everything work as expected, you can navigate to Portainer from the browser with the address http://localhost:30777
|
||||
|
||||
|
|
@ -50,9 +50,9 @@ Before you can deploy Portainer in Docker Standalone running in Windows, you nee
|
|||
|
||||
Use the following Docker commands to deploy the Portainer Server; note the agent is not needed on standalone hosts, however it does provide additional functionality if used (see portainer and agent scenario below):
|
||||
|
||||
<pre><code>$ docker volume create portainer_data</code></pre>
|
||||
<pre><code> docker volume create portainer_data</code></pre>
|
||||
|
||||
<pre><code>$ docker run -d -p 8000:8000 -p 9000:9000 --name=portainer --restart=always -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer-ce</code></pre>
|
||||
<pre><code> docker run -d -p 8000:8000 -p 9000:9000 --name=portainer --restart=always -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer-ce</code></pre>
|
||||
|
||||
### Docker Swarm in WSL2
|
||||
|
||||
|
|
@ -61,7 +61,7 @@ of the Portainer Server, and deploys the Portainer Agent as a global service on
|
|||
|
||||
Remember to initiate the Docker Swarm mode when you use Docker Desktop. You can do this running the following command:
|
||||
|
||||
<pre><code>$ docker swarm init</code></pre>
|
||||
<pre><code> docker swarm init</code></pre>
|
||||
|
||||
The terminal will reply with this:
|
||||
|
||||
|
|
@ -75,8 +75,8 @@ To add a manager to this swarm, run 'docker swarm join-token manager' and follow
|
|||
|
||||
Once this is done, you can continue with the installation running the following command:
|
||||
|
||||
<pre><code>$ curl -L https://downloads.portainer.io/portainer-agent-stack.yml -o portainer-agent-stack.yml</code></pre>
|
||||
<pre><code>$ docker stack deploy -c portainer-agent-stack.yml portainer</code></pre>
|
||||
<pre><code> curl -L https://downloads.portainer.io/portainer-agent-stack.yml -o portainer-agent-stack.yml</code></pre>
|
||||
<pre><code> docker stack deploy -c portainer-agent-stack.yml portainer</code></pre>
|
||||
|
||||
### Docker Standalone using Windows Containers
|
||||
|
||||
|
|
@ -86,8 +86,8 @@ Another scenario is running Docker in Windows is running Windows Containers. Thi
|
|||
|
||||
Once this is done, you need to open a PowerShell console and run the following commands:
|
||||
|
||||
<pre><code>$ docker volume create portainer_data</code></pre>
|
||||
<pre><code>$ docker run -d -p 9000:9000 --name portainer --restart always -v \\.\pipe\docker_engine:\\.\pipe\docker_engine -v portainer_data:C:\data portainer/portainer-ce</code></pre>
|
||||
<pre><code> docker volume create portainer_data</code></pre>
|
||||
<pre><code> docker run -d -p 9000:9000 --name portainer --restart always -v \\.\pipe\docker_engine:\\.\pipe\docker_engine -v portainer_data:C:\data portainer/portainer-ce</code></pre>
|
||||
|
||||
Now, you can navigate to http://localhost:9000 and start using Portainer.
|
||||
|
||||
|
|
@ -95,8 +95,8 @@ Now, you can navigate to http://localhost:9000 and start using Portainer.
|
|||
|
||||
You can use our YML manifest to run Portainer in Windows using Windows Containers. In a Powershell windows, you must run:
|
||||
|
||||
<pre><code>$ curl https://downloads.portainer.io/portainer_windows_stack.yml -o portainer_windows_stack.yml</code></pre>
|
||||
<pre><code>$ docker stack deploy --compose-file=portainer_windows_stack.yml portainer</code></pre>
|
||||
<pre><code> curl https://downloads.portainer.io/portainer_windows_stack.yml -o portainer_windows_stack.yml</code></pre>
|
||||
<pre><code> docker stack deploy --compose-file=portainer_windows_stack.yml portainer</code></pre>
|
||||
|
||||
## Deploy Portainer Agent in Windows running WSL
|
||||
|
||||
|
|
@ -108,7 +108,7 @@ Run the following command to deploy the Agent in your Docker host.
|
|||
### Docker Swarm
|
||||
Deploy Portainer Agent on a remote LINUX Swarm Cluster as a Swarm Service, run this command in a manager node in the remote cluster.
|
||||
|
||||
<pre><code>$ docker service create --name portainer_agent --network portainer_agent_network --publish mode=host,target=9001,published=9001 -e AGENT_CLUSTER_ADDR=tasks.portainer_agent --mode global --mount type=bind
|
||||
<pre><code> docker service create --name portainer_agent --network portainer_agent_network --publish mode=host,target=9001,published=9001 -e AGENT_CLUSTER_ADDR=tasks.portainer_agent --mode global --mount type=bind
|
||||
src=//var/run/docker.sock,dst=/var/run/docker.sock --mount type=bind,src=//var/lib/docker/volumes,dst=/var/lib/docker/volumes –-mount type=bind,src=/,dst=/host portainer/agent</code></pre>
|
||||
|
||||
## Deploy Portainer Agent in Windows using Windows Containers.
|
||||
|
|
|
|||
|
|
@ -26,8 +26,8 @@ Lastly, you need to restart your Windows Server. After it has restarted, you're
|
|||
|
||||
### Docker Standalone
|
||||
|
||||
<pre><code>$ docker volume create portainer_data</code></pre>
|
||||
<pre><code>$ docker run -d -p 9000:9000 --name portainer --restart always -v \\.\pipe\docker_engine:\\.\pipe\docker_engine -v portainer_data:C:\data portainer/portainer-ce</code></pre>
|
||||
<pre><code> docker volume create portainer_data</code></pre>
|
||||
<pre><code> docker run -d -p 9000:9000 --name portainer --restart always -v \\.\pipe\docker_engine:\\.\pipe\docker_engine -v portainer_data:C:\data portainer/portainer-ce</code></pre>
|
||||
|
||||
Now, you can navigate to http://localhost:9000 or the IP of the server and start using Portainer.
|
||||
|
||||
|
|
@ -35,8 +35,8 @@ Now, you can navigate to http://localhost:9000 or the IP of the server and start
|
|||
|
||||
You can use our YML manifest to run Portainer in Windows using Windows Containers. In Powershell, run:
|
||||
|
||||
<pre><code>$ curl https://downloads.portainer.io/portainer_windows_stack.yml -o portainer_windows_stack.yml</code></pre>
|
||||
<pre><code>$ docker stack deploy --compose-file=portainer_windows_stack.yml portainer</code></pre>
|
||||
<pre><code> curl https://downloads.portainer.io/portainer_windows_stack.yml -o portainer_windows_stack.yml</code></pre>
|
||||
<pre><code> docker stack deploy --compose-file=portainer_windows_stack.yml portainer</code></pre>
|
||||
|
||||
Now, you can navigate to http://localhost:9000 or the IP of the server and start using Portainer.
|
||||
|
||||
|
|
|
|||
|
|
@ -16,11 +16,11 @@ Once you have deployed portainer (see [Deploying Portainer](../deploy/requiremen
|
|||
|
||||
## Initialize the admin password
|
||||
|
||||
<pre><code>$ http POST :9000/api/users/admin/init Username="admin" Password="adminpassword"</code></pre>
|
||||
<pre><code> http POST :9000/api/users/admin/init Username="admin" Password="adminpassword"</code></pre>
|
||||
|
||||
## Authenticate against the API using the admin account
|
||||
|
||||
<pre><code>$ http POST :9000/api/auth Username="admin" Password="adminpassword"</code></pre>
|
||||
<pre><code> http POST :9000/api/auth Username="admin" Password="adminpassword"</code></pre>
|
||||
|
||||
The response is a JSON object containing the JWT token inside the jwt field:
|
||||
|
||||
|
|
@ -42,7 +42,7 @@ This query will create an endpoint called <b>test-local</b> and will use the Doc
|
|||
|
||||
<b>NOTE:</b> This example requires to you bind-mount the Docker socket when running Portainer. Run the following:
|
||||
|
||||
<pre><code>$ http --form POST :9000/api/endpoints \
|
||||
<pre><code> http --form POST :9000/api/endpoints \
|
||||
"Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6MSwidXNlcm5hbWUiOiJhZG1pbiIsInJvbGUiOjEsImV4cCI6MTQ5OTM3NjE1NH0.NJ6vE8FY1WG6jsRQzfMqeatJ4vh2TWAeeYfDhP71YEE" \
|
||||
Name="test-local" EndpointType=1</code></pre>
|
||||
|
||||
|
|
@ -73,7 +73,7 @@ This query will create an endpoint called <b>test-remote</b> and will communicat
|
|||
|
||||
<b>NOTE:</b> The Docker API must be exposed on that IP address & port. Please refer to the Docker documentation to check how to configure this.
|
||||
|
||||
<pre><code>$ http --form POST :9000/api/endpoints \
|
||||
<pre><code> http --form POST :9000/api/endpoints \
|
||||
"Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6MSwidXNlcm5hbWUiOiJhZG1pbiIsInJvbGUiOjEsImV4cCI6MTQ5OTM3NjE1NH0.NJ6vE8FY1WG6jsRQzfMqeatJ4vh2TWAeeYfDhP71YEE" \
|
||||
Name="test-remote" URL="tcp://10.0.7.10:2375" EndpointType=1</code></pre>
|
||||
|
||||
|
|
@ -104,7 +104,7 @@ This query will create an endpoint called <b>test-remote-tls</b> and will commun
|
|||
|
||||
<b>NOTE:</b> The Docker API must be exposed on that IP address & port. Please refer to the Docker documentation to check how to configure this.
|
||||
|
||||
<pre><code>$ http --form POST :9000/api/endpoints \
|
||||
<pre><code> http --form POST :9000/api/endpoints \
|
||||
"Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6MSwidXNlcm5hbWUiOiJhZG1pbiIsInJvbGUiOjEsImV4cCI6MTQ5OTM3NjE1NH0.NJ6vE8FY1WG6jsRQzfMqeatJ4vh2TWAeeYfDhP71YEE" \
|
||||
Name="test-remote" URL="tcp://10.0.7.10:2376" EndpointType=1 TLS="true" TLSCACertFile@/path/to/ca.pem TLSCertFile@/path/to/cert.pem TLSKeyFile@/path/to/key.pem</code></pre>
|
||||
|
||||
|
|
|
|||
|
|
@ -117,7 +117,7 @@ Portainer Edge agent successfully deployed</code></pre>
|
|||
|
||||
You can validate if the Edge Agent is running in your host executing the following command:
|
||||
|
||||
<pre><code>$ kubectl get pods --namespace=portainer</code></pre>
|
||||
<pre><code> kubectl get pods --namespace=portainer</code></pre>
|
||||
|
||||
After running the command, you can enter the IP address of the host and click in <b>Update Endpoint</b> button.
|
||||
|
||||
|
|
|
|||
|
|
@ -32,7 +32,7 @@ deployment.apps/portainer-agent created</code></pre>
|
|||
|
||||
To validate if the Agent is running, you can run the following command:
|
||||
|
||||
<pre><code>$ kubectl get pods --namespace=portainer</code></pre>
|
||||
<pre><code> kubectl get pods --namespace=portainer</code></pre>
|
||||
|
||||
The result of that command should be something like this:
|
||||
|
||||
|
|
@ -103,7 +103,7 @@ deployment.apps/portainer-agent created</code></pre>
|
|||
|
||||
To validate is the Agent is running, you can run the following command:
|
||||
|
||||
<pre><code>$ kubectl get pods --namespace=portainer</code></pre>
|
||||
<pre><code> kubectl get pods --namespace=portainer</code></pre>
|
||||
|
||||
The result of that command should be something like this:
|
||||
|
||||
|
|
|
|||
|
|
@ -26,7 +26,7 @@ Creating service portainer-agent_agent</code></pre>
|
|||
|
||||
To validate is the Agent is running, you can run the following command:
|
||||
|
||||
<pre><code>$ docker service ls</code></pre>
|
||||
<pre><code> docker service ls</code></pre>
|
||||
|
||||
The result of that command should be something like this:
|
||||
|
||||
|
|
|
|||
|
|
@ -46,7 +46,7 @@ We are aware that the <code>--external-endpoint</code> feature is not working in
|
|||
|
||||
If you want to manage a local Docker environment with SELinux enabled, you’ll need to pass the --privileged flag to the Docker run command when deploying Portainer:
|
||||
|
||||
<pre><code>$ docker run -d --privileged -p 9000:9000 -p 8000:8000 --name portainer --restart always -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer-ce</code></pre>
|
||||
<pre><code> docker run -d --privileged -p 9000:9000 -p 8000:8000 --name portainer --restart always -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer-ce</code></pre>
|
||||
|
||||
You can also have a look at this [helper](https://github.com/dpw/selinux-dockersock.).
|
||||
|
||||
|
|
@ -54,7 +54,7 @@ You can also have a look at this [helper](https://github.com/dpw/selinux-dockers
|
|||
|
||||
With Portainer behind a proxy, some features requiring access to the Internet (such as Apps Templates) might be unavailable. When running Portainer as a container, you can set the HTTP_PROXY and HTTPS_PROXY env vars to specify which proxy should be used:
|
||||
|
||||
<pre><code>$ docker run -d -p 9000:9000 -p 8000:8000 -e HTTP_PROXY=my.proxy.domain:7777 portainer/portainer-ce</code></pre>
|
||||
<pre><code> docker run -d -p 9000:9000 -p 8000:8000 -e HTTP_PROXY=my.proxy.domain:7777 portainer/portainer-ce</code></pre>
|
||||
|
||||
For examples on how to configure a reverse proxy to work with Portainer, you can refer to our example repo here.
|
||||
|
||||
|
|
|
|||
|
|
@ -8,11 +8,11 @@ Reset the password for the Admin user can be accomplished using our reset [passw
|
|||
|
||||
First, stop the Portainer container by running:
|
||||
|
||||
<pre><code>$ docker stop "id-portainer-container"</code></pre>
|
||||
<pre><code> docker stop "id-portainer-container"</code></pre>
|
||||
|
||||
Run the helper with the following command. Be advised that you need to mount the Portainer data volume.
|
||||
|
||||
<pre><code>$ docker run --rm -v portainer_data:/data portainer/helper-reset-password</code></pre>
|
||||
<pre><code> docker run --rm -v portainer_data:/data portainer/helper-reset-password</code></pre>
|
||||
|
||||
If successful, your output should look like this:
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue