Docker Windows strange ownership directory change and other issues with Windows 10 #46574
Unanswered
MoctezumaDev
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi, I have been trying some images from GameCI group and also some custom images to run Unity3d on a container.
I created a few images using "mcr.microsoft.com/windows:1809" as the base of my images.
I kept using ContainerAdministrator as the default user and run everything without major issues.
I also have to run everything without Hyper-V since Unity3d licensing stuff seems to always fail if Hyper-V is used.
I always install docker by using the following script and not docker desktop:
Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/Windows-Containers/Main/helpful_tools/Install-DockerCE/install-docker-ce.ps1" -o install-docker-ce.ps1
We were executing this docker daemon on a Windows Server 2019 Version 1809 OSBuild 17763.4645 on Azure Cloud VM without problems.
The issues started when we tried to migrate the set-up to a physical machine on our office with Window 10.
The major difference seems to be that when our Gitlab-Runner tries to checkout the code the directory ownership is not the same than the "whoami" user which was not the case when running it on the Azure Cloud VM.
user manager\containeradministrator
Maybe the whole problem is the mismatch between the image and the host OS.
Some process seem to fail when trying to write in the cloned directory and also some DLLs get locked after being used some behavior that I didn't experience on the Azure Cloud VM.
Could someone bring me some light on this issue?
Beta Was this translation helpful? Give feedback.
All reactions