docker-swarm

问题 As described at Quarkus website that it is "Kubernetes native Java framework". Does that means it cannot be used for other Docker Orchestration platforms like DockerSwarm ? or it is just only optimized for K8S ? Regards. 回答1: Once you build a docker image, nothing stops you for using it with the container orchestration platform of your choice such as Docker Swarm. 来源： https://stackoverflow.com/questions/58154184/is-quarkus-optimized-for-docker-container-runtime-or-it-is-just-for-kubernetes

问题 As described at Quarkus website that it is "Kubernetes native Java framework". Does that means it cannot be used for other Docker Orchestration platforms like DockerSwarm ? or it is just only optimized for K8S ? Regards. 回答1: Once you build a docker image, nothing stops you for using it with the container orchestration platform of your choice such as Docker Swarm. 来源： https://stackoverflow.com/questions/58154184/is-quarkus-optimized-for-docker-container-runtime-or-it-is-just-for-kubernetes

问题 We have created a docker compose file with multiple services. The images for these services are built in runtime using 'build' configuration option. The corresponding Dockerfile(s) are given in the respective directories. Sample docker compose file... version: '3' services: db2server: build: ./db2server ports: - "50005:50000" command: ["db2start"] appruntime: build: ./appruntime depends_on: - db2server This docker compose file works with docker-compose command. The images are built in runtime

问题 We have created a docker compose file with multiple services. The images for these services are built in runtime using 'build' configuration option. The corresponding Dockerfile(s) are given in the respective directories. Sample docker compose file... version: '3' services: db2server: build: ./db2server ports: - "50005:50000" command: ["db2start"] appruntime: build: ./appruntime depends_on: - db2server This docker compose file works with docker-compose command. The images are built in runtime

问题 I have two machines running Ubuntu 16.04 LTS, on which I've installed Docker 18.03.1-ce. I created a swarm between the two hosts which is mostly working (I can deploy services and they show up, etc.). The only problem is that I'm not able to connect to the published ports of the services via any of the nodes' IPs, as described multiple times in the Docker documentation, unless the service is running on that particular node. In other words, if a service is deployed on node A and listening on

问题 I'm running nginx via lets-nginx in the default nginx configuration (as per the lets-nginx project) in a docker swarm: services: ssl: image: smashwilson/lets-nginx networks: - backend environment: - EMAIL=sas@finestructure.co - DOMAIN=api.finestructure.co - UPSTREAM=api:5000 ports: - "80:80" - "443:443" volumes: - letsencrypt:/etc/letsencrypt - dhparam_cache:/cache api: image: registry.gitlab.com/project_name/image_name:0.1 networks: - backend environment: - APP_SETTINGS=/api.cfg configs: -

问题 I want to run traefik on a docker swarm cluster powered by Windows Server 2019. It works while using docker network create and docker service create commands directly. But a seemingly identical compose file does not work. Any help is appreciated. PowerShell commands: # create network docker network create proxy --driver overlay --subnet 11.0.0.0/24 --gateway 11.0.0.1 # start traefik docker service create ` --name traefik ` --constraint node.role==manager ` --publish 80:80 ` --publish 8080

问题 I want to run traefik on a docker swarm cluster powered by Windows Server 2019. It works while using docker network create and docker service create commands directly. But a seemingly identical compose file does not work. Any help is appreciated. PowerShell commands: # create network docker network create proxy --driver overlay --subnet 11.0.0.0/24 --gateway 11.0.0.1 # start traefik docker service create ` --name traefik ` --constraint node.role==manager ` --publish 80:80 ` --publish 8080

问题 Is there any option to have the hostname / containername to have some seq numbers in case of replicas/scale in docker swarm? version: '3' services: serA: image: someimage1 hostname: serA serB: image: someimage2 tty: true hostname: serB{{.Node.index}} deploy: replicas: 2 For ex: I would like to have the hostnames as serB1 and serB2 回答1: AFAIK this is not supported and won't be supported as the Docker team thinks it's a bad idea: After some thought, I don't think this is a good idea. We might

问题 Is there any option to have the hostname / containername to have some seq numbers in case of replicas/scale in docker swarm? version: '3' services: serA: image: someimage1 hostname: serA serB: image: someimage2 tty: true hostname: serB{{.Node.index}} deploy: replicas: 2 For ex: I would like to have the hostnames as serB1 and serB2 回答1: AFAIK this is not supported and won't be supported as the Docker team thinks it's a bad idea: After some thought, I don't think this is a good idea. We might