Dinghy nfs volume permissions are super convenient - similar behavior on Linux host without nfs?

[gkop]

Thanks for dinghy! It's awesome for development on Mac :)

Going out on a limb here - I switched from a Mac host to Debian, and am missing the behavior of my dinghy setup where when my docker container process running as root creates a new file in a volume shared from the host, that file shows up on the host with the permissions of the host user. (On Linux, it gets root permissions)

Maybe some Dinghy users are on a team with Linux people? How do your Linux colleagues solve this problem?

[codekitchen]

Heh yes, we have a half dozen or so devs using Linux laptops. I wish I had a good answer, it's still a thorny problem for us. So far we've had to tweak each project to work on Linux as it's come up, by doing things such as hard-coding the UID inside the image, and then chown'ing the dev's local repo to match. See for example https://github.com/instructure/canvas-lms/blob/stable/doc/development_with_docker.md#troubleshooting

I'd love to hear from anybody else who has dealt with this, as well.

[dmitrym0]

Have you seen this? Using --userns-remap to map a UID inside the container with a real user. Thoughts?

[paolomainardi]

@dmitrym0 that flag is not compatible with volumes, so quite useless.

[dmitrym0]

@paolomainardi I'm not sure I understand. The flag allows to map container UID to a host UID. Docker then writes files out to the host with the specified UID.