docker-swarm

问题 We are using Artifactory pro 5.10.4 version. We are migating from a simple installation on a VM and apache reverse proxy for docker registries to docker swarm cluster. We are convinced that Traefik is the best alternative when it comes to dynamic configuration. We are facing some docker push with traefik. Our compose file for Artifactory service is: version: '3.7' services: artifactory: image: docker.bintray.io/jfrog/artifactory-pro:5.10.4 environment: EXTRA_JAVA_OPTIONS : > '-Xms2g' '-Xmx2g'

问题 I have troubles to make my HDFS setup work in docker swarm. To understand the problem I've reduced my setup to the minimum : 1 physical machine 1 namenode 1 datanode This setup is working fine with docker-compose, but it fails with docker-swarm, using the same compose file. Here is the compose file : version: '3' services: namenode: image: uhopper/hadoop-namenode hostname: namenode ports: - "50070:50070" - "8020:8020" volumes: - /userdata/namenode:/hadoop/dfs/name environment: - CLUSTER_NAME

问题 I need to run containers from docker-compose in host network mode. For example, if I run single container, I write: docker run --net=host my_image How to do this part --net=host in docker-compose? 回答1: The equivalent in docker-comopose is network_mode: host see the documentation in: https://docs.docker.com/compose/compose-file/ 来源： https://stackoverflow.com/questions/44658101/how-to-run-docker-containers-in-host-network-mode-using-docker-compose

问题 I need to run containers from docker-compose in host network mode. For example, if I run single container, I write: docker run --net=host my_image How to do this part --net=host in docker-compose? 回答1: The equivalent in docker-comopose is network_mode: host see the documentation in: https://docs.docker.com/compose/compose-file/ 来源： https://stackoverflow.com/questions/44658101/how-to-run-docker-containers-in-host-network-mode-using-docker-compose

问题 Right now I have a Python Application which runs 50 threads to process data. It takes an xlsx file and will process a list of values, and will output a simple csv. I said to myself, since this is a simple Python App with 50 threads, How can I create a cluster to distribute data-processing even more? FOR EXAMPLE: Have each Worker node process a subset given to it by the master. Well that sounds easy, just take the master app slice up the dataset generated and then push it to the workers with

问题 can i set “MemorySwap” and “MemorySwappiness” for docker service? I would like to disable memory swap for docker containers (started by docker service) but i don’t want to disable it for host machine. What means value of -1 at “MemorySwappiness”? Docker version: 17.06.2-ce 回答1: Although this question is old, as it has no answer I have decided to post one. Indeed, disabling memory swap is now supported by just using the option --memory-swap when creating the container. You simply have to set -

问题 can i set “MemorySwap” and “MemorySwappiness” for docker service? I would like to disable memory swap for docker containers (started by docker service) but i don’t want to disable it for host machine. What means value of -1 at “MemorySwappiness”? Docker version: 17.06.2-ce 回答1: Although this question is old, as it has no answer I have decided to post one. Indeed, disabling memory swap is now supported by just using the option --memory-swap when creating the container. You simply have to set -

问题 Last week I had to remove a failed node from my Docker Swarm Cluster, leaving some tasks that ran on that node in desired state "Remove". Even after deleting the stack and recreating it with the same name, docker stack ps stackname still shows them. Interestingly enough, after recreating the stack, the tasks are still there, but with no node assigned. Here's what I tried so far to "cleanup" the stack: Recreating the stack with the same name docker container prune docker volume prune docker

问题 Last week I had to remove a failed node from my Docker Swarm Cluster, leaving some tasks that ran on that node in desired state "Remove". Even after deleting the stack and recreating it with the same name, docker stack ps stackname still shows them. Interestingly enough, after recreating the stack, the tasks are still there, but with no node assigned. Here's what I tried so far to "cleanup" the stack: Recreating the stack with the same name docker container prune docker volume prune docker

问题 Last week I had to remove a failed node from my Docker Swarm Cluster, leaving some tasks that ran on that node in desired state "Remove". Even after deleting the stack and recreating it with the same name, docker stack ps stackname still shows them. Interestingly enough, after recreating the stack, the tasks are still there, but with no node assigned. Here's what I tried so far to "cleanup" the stack: Recreating the stack with the same name docker container prune docker volume prune docker