docker-swarm

问题 I tried to create services in docker swarm model by following this document I created two nodes in the swarm: Then create the deploy the service, I use jwilder/whoami here instead of nginx in the document, docker service create --name my-web --publish published=8888,target=8000 --replicas 2 jwilder/whoami Seems like they started successfully: As the document said: When you access port 8080 on any node, Docker routes your request to an active container. SO in my opinion, I can access the my

问题 I tried to create services in docker swarm model by following this document I created two nodes in the swarm: Then create the deploy the service, I use jwilder/whoami here instead of nginx in the document, docker service create --name my-web --publish published=8888,target=8000 --replicas 2 jwilder/whoami Seems like they started successfully: As the document said: When you access port 8080 on any node, Docker routes your request to an active container. SO in my opinion, I can access the my

问题 I tried to create services in docker swarm model by following this document I created two nodes in the swarm: Then create the deploy the service, I use jwilder/whoami here instead of nginx in the document, docker service create --name my-web --publish published=8888,target=8000 --replicas 2 jwilder/whoami Seems like they started successfully: As the document said: When you access port 8080 on any node, Docker routes your request to an active container. SO in my opinion, I can access the my

问题 We have a networking problem in docker-swarm. The problem is below; we have virtualized environment over wmware ( vsphere 6.02) our servers are created from vmware say server1 and server2 we have a docker compose file defining a couple of services we have an overlay-network definition within docker-compose for docker-swarm when we deploy system using docker-swarm deployment is finished successfully, all containers gets ip from overlay network range. But the problem is if 2 containers (say

问题 We have a networking problem in docker-swarm. The problem is below; we have virtualized environment over wmware ( vsphere 6.02) our servers are created from vmware say server1 and server2 we have a docker compose file defining a couple of services we have an overlay-network definition within docker-compose for docker-swarm when we deploy system using docker-swarm deployment is finished successfully, all containers gets ip from overlay network range. But the problem is if 2 containers (say

问题 We have a networking problem in docker-swarm. The problem is below; we have virtualized environment over wmware ( vsphere 6.02) our servers are created from vmware say server1 and server2 we have a docker compose file defining a couple of services we have an overlay-network definition within docker-compose for docker-swarm when we deploy system using docker-swarm deployment is finished successfully, all containers gets ip from overlay network range. But the problem is if 2 containers (say

问题 I really enjoy the concept of having a cluster of docker machines available to execute docker services. I also like the additional features not available to singular docker containers (such as docker secret). But I really have no need for long-standing services. My use case is to simply execute a bash script to use the docker swarm to take in an arbitrary number of finite commands, and execute each as a running docker container on the same docker image, while using the secrets loaded up with

问题 Here is exactly what I need. I already have a project which is starting up a particular set of docker images and it works completely fine. But I want to create another image, which is particularly to build this project from the scratch having all the dependencies inside. So, the problem is, when building, to create docker images, we need to access the docker daemon running on the host machine from the building container. Is there any way of doing this? 回答1: If you need to access docker on the

问题 I'm having trouble pulling images from AWS ECR, running Docker Swarm. It's been working ok for years, but my swarm manager nodes were changed to new EC2 instances. Now my services fail to deploy: ~ $ docker stack deploy -c dkr_compose_geo_site:3.2.0 --with-registry-auth geo_stack The manager node log shows "no basic auth credentials": May 19 21:21:12 ip-172-31-3-108 root: time="2020-05-19T21:21:12.857007050Z" level=error msg="pulling image failed" error="Get https://445523.dkr.ecr.us-west-2

问题 Using: Docker Desktop for Windows 10 MobaXterm to RDP into a Windows 10 VM Selenium 3.141.59 I'm currently trying to run a selenium Grid within a docker container and I'm encountering some issues. I have both Hyper-V and Containers enabled on both my PC and the VM. The problem is that unlike my previous coworkers, I'm using a Windows VM instead of a Linux one. When I try to run docker within the virtual machine it says that I need to enable nested virtualization. Is this correct or should I