Credentials needs to be reset again and again

Docker Desktop
1

I’m running into the same issue. I have two drives shared (F: & G:) where my projects are stored.

I’m creating my container something along this :

docker run -d -p 80:80 -p 3306:3306 -v G:\\__SOURCES\projectname\:/var/www --name project custom:container

Everything works fine for a while, then at some point, the volume will lose its rights and I will get (for exemple) :

root@c7c4a0903d5c:/var/www# ls
ls: reading directory .: Permission denied

If I go to Settings, Shared Drives and click “Apply” or “Reset credentials”, everything will works fine again, until some random event makes the rights lost.

The container I’m launching is a basic ubuntu with a bunch of web dev stuff installed (apache, mysql,you get the idea).

I’m using Docker for Windows, version 1.12.5 and 1.13.0-rc5 build 43cc971, under Windows 10 pro, no domain joined, logging with a microsoft account.

If anyone had the slightest idea what could cause that (or how I can find out), and even better how to fix it, I’m all ears.

Thanks !

2

Also, when the credentials are “old”, trying to start a container gives the following error :

C:\Program Files\Docker\Docker\Resources\bin\docker.exe: Error response from daemon: oci runtime error: container_linux.go:247: starting container process caused “process_linux.go:359: container init caused "rootfs_linux.go:54: mounting \"/G/__SOURCES/projectname/\" to rootfs \"/var/lib/docker/aufs/mnt/4b3252fe8a78b3092080cb514c8a6088bbbe1b4186f70f405e9e130cb7530b47\" at \"/var/www\" caused \"stat /G/__SOURCES/projectname: permission denied\""”.

Same than before, just clicking “Apply” in the volume setting pane fix this.

3

I am having the same issue with my docker container. I have a Microsoft SQL Server 2017 container running on Windows 10 and I have the /var/opt/mssql folder shared to my C:\SQLData2017 folder to persist the databases. It seems that every time I reboot my laptop it loses the credentials and I have to reset and re-enter them to get the container to start back up.

So far I have not found a solution for this.