9

I am having problem sharing a folder between Docker containers running on different nodes of Docker Swarm. My swarm consist of one manager and two workers.

I am using this compose file to deploy applications:

version: '3'

services:

  redis:
    image:
      redis:latest
    networks:
      - default
    ports:
      - 6379:6379
    volumes:
      - test-volume:/test
    deploy:
      replicas: 1
      update_config:
        parallelism: 2
        delay: 10s
      restart_policy:
        condition: on-failure
      placement:
        constraints: [node.role == manager]

  logstash:
    image: docker.elastic.co/logstash/logstash:5.2.2
    networks:
      - default
    volumes:
      - test-volume:/test
    deploy:
      placement:
        constraints: [node.role == worker]

networks:
  default:
    external: false

volumes:
  test-volume:

I can confirm that the folder is successfully mounted in both containers with use of docker exec _id_ ls /test. But when I add a file into this folder with docker exec _id_ touch /test/file second container does not see created file.

How to configure the swarm so the files are visible in both containers?

Marek J
  • 1,364
  • 8
  • 18
  • 33
  • I found this article: maybe it'll be useful: https://ender74.github.io/Sharing-Volumes-With-Docker-Swarm/ . I didn't know that it works this way and as someone answered - plugin may be needed to achieve your goal. – barat Mar 08 '17 at 16:23

1 Answers1

33

Volumes created in docker swarm via default driver are local to the node. So if you put both containers on the same host they will have a shared volume. But when you put your containers on different nodes, there will be a separate volume created on each node.

Now in order to achieve bind mounts/volumes across multiple nodes you have these options:

  1. Use a cluster filesystem like glusterfs, ceph and ... across swarm nodes, then use bind mounts in your service defenition pointing to shared fs.

  2. Use one of the many storage drivers available to docker that provide shared storage like flocker, ...

  3. Switch to Kubernetes and take advantage of automated volume provisioning using multiple backends via Storage classes and claims.

UPDATE: As @Krishna noted in the comments Flocker has been shut down and there isn't a lot of activity on the github repo.

Farhad Farahi
  • 35,528
  • 7
  • 73
  • 70
  • 7
    Flocker has been [shut down](https://clusterhq.com/2016/12/22/clusterf-ed/) and there isn't a lot of activity on the [github repo](https://github.com/ClusterHQ/flocker). – Krishna Mar 29 '17 at 15:03
  • So basically the only option is to use bind mounts with a cluster filesystem? Currently, I have my Postgres container placed on my only manager in the cluster with a traditional local volume. Do you have any other suggestions? – Yannic Hamann Feb 27 '19 at 08:11