docker-swarm

问题 I need a service within a Docker Swarm stack which has one additional interface based on a macvlan network. This is cause the JBoss Cluster in this service needs to communicate via IP multicast, which is currently not supported in overlay networks. I have created the macvlan network like that: # Worker 1: docker network create --config-only --subnet 10.140.0.0/16 -o parent=ens224.800 --ip-range 10.140.1.0/24 swarm-multicast-config-only # Worker 2: docker network create --config-only --subnet

问题 I need a service within a Docker Swarm stack which has one additional interface based on a macvlan network. This is cause the JBoss Cluster in this service needs to communicate via IP multicast, which is currently not supported in overlay networks. I have created the macvlan network like that: # Worker 1: docker network create --config-only --subnet 10.140.0.0/16 -o parent=ens224.800 --ip-range 10.140.1.0/24 swarm-multicast-config-only # Worker 2: docker network create --config-only --subnet

问题 I have 3 VM's. They all have docker 1.12 and they are running on centos7. All the ports are opened and the vm's are able to ping eachother I started my cluster with docker swarm init --advertise-addr 192.168.140.12 Docker info showed me: Swarm: active NodeID: 0drcj2nku1mv8t16fxva48edxx Is Manager: true ClusterID: cchn0yzospwoe1h9f55d7omxx Managers: 1 Nodes: 1 Now I try to join nodes (other vms) to the cluster. I use the command which was recommended after starting my manager. docker swarm

问题 I have 3 VM's. They all have docker 1.12 and they are running on centos7. All the ports are opened and the vm's are able to ping eachother I started my cluster with docker swarm init --advertise-addr 192.168.140.12 Docker info showed me: Swarm: active NodeID: 0drcj2nku1mv8t16fxva48edxx Is Manager: true ClusterID: cchn0yzospwoe1h9f55d7omxx Managers: 1 Nodes: 1 Now I try to join nodes (other vms) to the cluster. I use the command which was recommended after starting my manager. docker swarm

问题 I am evaluating Kubernetes (with Docker containers, not Kubernetes) and Docker Swarm and could use your input. If I'm looking at 3 (8.76 hours) or 4 (52 min) 9's reliability in a server farm that is < 100 servers, would Kubernetes be overkill due to its complexity? Would Docker Swarm suffice? 回答1: Docker swarm will be able to meet your requirements. I recommend you start with Docker swarm as it is robust and very straightforward to use for anyone who has used Docker before. For a Docker user,

问题 I have created one service and exposed it to run only on localhost in one of my docker swarm node but I can access the service publicly too easily. I have deleted and redeployed the docker stack but still same issue. Here is my docker-compose.yml I have used to deploy the service in stack version: "3" networks: api-net: ipam: config: - subnet: 10.0.10.0/24 services: health-api: image: myprivateregistry:5000/healthapi:qa ports: - "127.0.0.1:9010:9010" networks: - api-net depends_on: - config

问题 I have a problem with deploying local virtualbox based swarm - I have followed the instructions in the official docker documentation regarding setting up master/worker nodes using the docker-machine tool. I have created the token on dockerhub and used --swarm (and --swarm-master) with --swarm-discovery token://XXXX ... so far so good, two machines running, seemingly registered as the Swarm master and worker: spaceback@brutus:~$ docker-machine ls NAME ACTIVE DRIVER STATE URL SWARM DOCKER

问题 I have a problem with deploying local virtualbox based swarm - I have followed the instructions in the official docker documentation regarding setting up master/worker nodes using the docker-machine tool. I have created the token on dockerhub and used --swarm (and --swarm-master) with --swarm-discovery token://XXXX ... so far so good, two machines running, seemingly registered as the Swarm master and worker: spaceback@brutus:~$ docker-machine ls NAME ACTIVE DRIVER STATE URL SWARM DOCKER

问题 I cannot connect to a service running on docker swarm. The swarm seems ok because I can connect to other containers running on it. I running the service with docker stack deploy -c docker-compose.yaml nifi and the docker compose file is: version: "3.3" services: registry: image: apache/nifi-registry:0.3.0 ports: - "18080:18080" deploy: replicas: 1 restart_policy: condition: on-failure When I run this without the swarm i.e. docker-compose -f docker-compose.yaml up it works fine and I can

问题 I'm deploying some images from my registry into my application server using docker swarm mode hos t : My image in the registry is looking like this (executing docker images ) : REPOSITORY TAG IMAGE ID CREATED SIZE localhost:5000/myApp G02R00C09_myTag c1fc2242f9a0 2 hours ago 272MB Under my docker compose file , my service looks like this : --- version: '3.4' services: ihm: image: myRegistryServer:5000/myApp:G02R00C09_myTag stdin_open: true volumes: - /opt/logs:/opt/logs tty: true ports: -