resin-io/chat

@valentinalexeev I'm not sure I understand what you are trying to do.
So far I gather:

• there's one service that should have a volume at /config
• another service might access that in a shared volume, that you want to mount inside another existing volume?

I think the important part is that you can have volumes and mount them in different places in different service, don't have to be at the same place. Just set their internal endpoint to the right one your service needs. So for a simplified version, here's a docker-compose.yml, that you can try on your development machine (if you have docker and docker compose installed) with docker-compose run, so you can play with the volumes:

version: '2.1'
services:
  service1:
    image: "alpine"
    command: touch /config/test
    volumes:
      - service1-config:/config
  service2:
    image: "alpine"
    command: ls -la /data/other-config
    volumes:
      - resin-data:/data
      - service1-config:/data/other-config
    depends_on:
      - service1

volumes:
  resin-data:
  service1-config:

This will result in something like:

$ docker-compose up
Starting volumes_service1_1 ... done
Starting volumes_service2_1 ... done
Attaching to volumes_service1_1, volumes_service2_1
service2_1  | total 8
volumes_service1_1 exited with code 0
service2_1  | drwxr-xr-x    2 root     root          4096 Apr  9 17:20 .
service2_1  | drwxr-xr-x    3 root     root          4096 Apr  9 17:18 ..
service2_1  | -rw-r--r--    1 root     root             0 Apr  9 17:24 test
volumes_service2_1 exited with code 0

thus in service2 you can see the test file created by service1.