No as the container is not launched using docker but using jenkins kubernetes plugin as a pod where the UID needed is 1000: https://github.com/jenkinsci/kubernetes-plugin#pipeline-sh-step-hangs-when-multiple-containers-are-used
On Wednesday, June 16, 2021 at 10:14:44 PM UTC+2 [email protected] wrote: > Have you tried -u root while running the container? > > On Thu, 17 Jun, 2021, 1:35 am Charles Moulliard, <[email protected]> > wrote: > >> Hi >> >> One of our container is reporting a permission denied as git cannot write >> a file on the filesystem mounted. As the uid used during the pod creation >> to allow the jenkins jnlp client to work correctly is 1000, what should we >> do to design correctly the image of that container to be able to give write >> permission even when the pod created will use as uid 1000 ? >> >> Cheers >> >> Charles >> >> -- >> 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/b973f0bc-210e-4a49-aaca-3936ada9b57cn%40googlegroups.com >> >> <https://groups.google.com/d/msgid/jenkinsci-users/b973f0bc-210e-4a49-aaca-3936ada9b57cn%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- 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/77786b52-017b-45c0-bcd7-2684dc8d3820n%40googlegroups.com.
