If this was not about hacking it would be a lot easier to accomplish. 😁 I found also out that it is good practice to add arguments to the dockerfile. This would then be the interface to pass in environment variables of jenkins. A good candidate could be WORKSPACE and extract uid and gid inforation from there.
Last but not least, we could patch and fix the dotnet cli tool to not require a valid user in the docker container... On 10 Jul 2017 10:33 a.m., "Stefan Bodewig" <[email protected]> wrote: > On 2017-07-10, Dominik Psenner wrote: > > > I just stumbled upon this which may allows us to detect the expected uid > > that a docker container is run in when the docker container is built. We > > can use that information to prepare the docker container user so that its > > uid and gid match the one we need later when the docker container is run: > > > https://github.com/bdruemen/jenkins-docker-uid-from- > volume/blob/master/Dockerfile > > looks like an intersting hack :-) > > Stefan >
