podman-compose how to support other host's mount device #787
Replies: 2 comments
-
the whole log display like exit code: 126 exit code: 125 i tried to debug and during build the image, also add cap_add sys_admin, but it still doesn't work |
Beta Was this translation helpful? Give feedback.
-
I've got pretty much the same problem and havent' been able to find any documentation the last two days looking on how to make it all work. I defined my nfs volumes in my docker-compose.yml and then when I podman-compose up -d it I get the same above error. |
Beta Was this translation helpful? Give feedback.
-
i tried to change the docker-compose to podman-compose
before the yaml file has the shared volumes like this
volumes:
test-data-nfs:
driver: local
driver_opts:
type: nfs
o: addr=10.0.148.162,ro,nolock,nosuid,nodev
device: :/test_data
the two services use it
tty: true
stdin_open: true
security_opt:
privileged is required by running podman in container
privileged: true
volumes:
working_dir: /code
command: /bin/bash
but when start it, it will display
Error: unable to start container "713a907311297cf0b801bf11d583521f164777743a297d626f86b1e25bd49c3d": mounting volume pub-test_test-data-nfs for container 713a907311297cf0b801bf11d583521f164777743a297d626f86b1e25bd49c3d: mount.nfs: Failed to resolve server : Name or service not known
Beta Was this translation helpful? Give feedback.
All reactions