Permission denied returned from a container due to uid used = 1000

[Charles Moulliard]

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

[uday kiran]

Have you tried -u root while running the container?

--
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 jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/b973f0bc-210e-4a49-aaca-3936ada9b57cn%40googlegroups.com.

[Charles Moulliard]

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

[Anderson Cruz]

Hello,

I had the same issue. Tried to force dockerfile and unix files fo force Umask but always some files belongs to user and group different from Jenkins Agent connected. 

Looks like a cascade shell inside Container invokes and overwrite 055 umask and ignore my directives ( or it's not propaged ).

My solution was all my nodes outside NIS system and using default jenkins user 1000 to connect.

Anderson Cruz

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/77786b52-017b-45c0-bcd7-2684dc8d3820n%40googlegroups.com.