/dev/*individually and enable
evdevunless we’re making the container privileged, is that correct?
@valentinalexeev I'm not sure I understand what you are trying to do.
So far I gather:
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
service2 you can see the
test file created by
service1-configvolume, not related to the
resin-datavolume at all (that volume alone is empty), and you don't need that. Just use the volumes you want to share between services, and set the internal mount points where you need them or want to use them. For example if
service1needs a volume mounted at
/config, that 's fine, in other service , maybe in
service2you control the code, just mount wherever it makes sense.
docker-compose.ymlthat you are trying to use?) then we can give more specific advice. Also would recommend posting it in our forums, where there's more chance to get feedback and quicker https://forums.balena.io/
sudo balena ssh --host ? Select a device morning-brook (547930d) Connecting to: 547930dc64fdd31d896673fd7d422162 firstname.lastname@example.org: Permission denied (publickey).