docker-compose up -f my-compose-file -f additional-compose-file -up d
docker stack deploy --compose-file my-compose-file --compose-file compose-additional-file
kubectl apply -f my-compose-file -f additional-compose-file
.envfile, which if it exists (and environment variables have not been previously defined) is processed as well.
docker ps), but we're discussing ways that we might be able to make this more user-friendly in the future.
[err: Cannot connect to the Docker daemon at tcp://tasks.portainer_agent:9001. Is the docker daemon running?]
[err: Error response from daemon: The agent was unable to contact any other agent located on a manager node]
1500. Hetzner's private networking, for example, uses a MTU of
1500, and if the underlying network has a lower MTU than this the Swarm nodes may fail to communicate with each other. This would affect all Swarm services, not just Portainer.
mtu. For example:
5: ens10: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc pfifo_fast state UP group default qlen 1000
ingressnetwork with the new value. You can use the following commands to achieve this:
4789by default which conflicts with VMware NSX's communication port for VXLAN.
[network]with the name of your network adapter. You will likely need to restart the services on your cluster that communicate with each other (such as the Portainer Agent) for this change to be picked up.
vmw_conn_notifydis being used. There is an open issue with VMware discussing the behavior which we are following, and is worth reading for potential workarounds until this is patched.
--http-disabledcommand line option) disables logging into Portainer via HTTP. If your HTTPS setup is misconfigured (for example a malformed or missing certificate chain) this can result in you being locked out of Portainer.
--http-enabledcommand line option in your docker run command, for example:
--http-enabled flag, you will be able to access Portainer over HTTP once more.
CONTAINER_IDof the Portainer container. Next, run the following command to output the logs for the container, using the
CONTAINER_IDfrom the previous command (in the above example,
https://localhost:9443with the URL and port of your Portainer server. You can then log in as the initial administrator user you first set up when installing Portainer.