Hi, so what is happening:
1. Jenkins starts up a docker container. 2. It connects as jenkins user 3. In your case, you try to create a workspace +aux. dirs on / (root level) as this user. While the real workspace is bind-mounted, jenkins attempts to create the aux.dir locally, but only root has write access there. Is it really essential to use a non-standard directory here? It is both non-standard in the jenkins sense, where workspace is typically a sub-dir of the jenkins user home, and non-standard according to the Filesystem Hierarchy Standard <https://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard> which makes thing much harder... Björn -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/c2b5859a-a442-49d5-b12a-0c3cb4f194a8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
