Hey Brandon,
Really appreciate the two suggestions. 🙂
For the first part: Yes, both systems are Linux based.
I’ll check for the root_squash setting. I wasn’t aware of this.
Permission wise, both mount point and share on each systems were owned by the same uid and gid. Also for some reason, it seemed to check for the name of the user rather than the uid, because once I set on the NAS root as the owner of the share, docker seemed to be happier. But I reverted back as I did not wanted root owning the share.
I had try to find the daemon to give it the proper uid, but did not realize it could be done by modifying docker.service. Still learning Docker, I used to run everything directly on dedicated VMs.
However, I like your second suggestion better as it’s way easier indeed, and it will do what I wanted, which is to have the data on the NAS and not on the VMs directly.
I’ll reset the Docker VM to start clean and will just map the share and bind mount it to containers.
Going that route, does the docker daemon still need to have the same uid as the one owning the share?
