Running jenkins/jnlp-agent-* Docker images as non-root user

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Running jenkins/jnlp-agent-* Docker images as non-root user

Damien Duportal-2

Hello dear Developers, Contributors and (eventually) users!

The issue https://issues.jenkins.io/browse/INFRA-2879 is making a proposal for a breaking change in the library of Docker images ("jenkins/jnlp-agent-*") coming from the repository https://github.com/jenkinsci/jnlp-agents .

The rationale of this change (why running a container as non root) is not expected to be discussed in this thread (please use the JIRA issue), but:

1. "Should we do this change"? As it even questions the reasons why we provide and maintain this set of images. For instance "jenkins/jnlp-agent-alpine" would be totally deprecated.

2. And if yes, "what is the process to communicate and apply a breaking change?". Is there a standard procedure to go trough the mail/twitter/IRC/etc. channels? We were thinking of adding documentation (README of the repo + README of the images in the DockerHub + comments in the respective Dockerfiles) and writing a blog post. Is there something else?

As the documentation for these image is scarse, it is hard to evaluate the impact. If you have any knowledge on how it is being used (outside the Jenkins project's infra.), could you share it to help us?


Thanks in advance!

Damien DUPORTAL




--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/6bba5b26-5070-4ad2-9a8a-ab0f3f3c96c4n%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: Running jenkins/jnlp-agent-* Docker images as non-root user

Oleg Nenashev
Parallel thread in Jenkins Infra: https://groups.google.com/g/jenkins-infra/c/DjUK9Ys82Mo
Put my answers there

On Wednesday, January 20, 2021 at 6:10:45 PM UTC+1 [hidden email] wrote:

Hello dear Developers, Contributors and (eventually) users!

The issue https://issues.jenkins.io/browse/INFRA-2879 is making a proposal for a breaking change in the library of Docker images ("jenkins/jnlp-agent-*") coming from the repository https://github.com/jenkinsci/jnlp-agents .

The rationale of this change (why running a container as non root) is not expected to be discussed in this thread (please use the JIRA issue), but:

1. "Should we do this change"? As it even questions the reasons why we provide and maintain this set of images. For instance "jenkins/jnlp-agent-alpine" would be totally deprecated.

2. And if yes, "what is the process to communicate and apply a breaking change?". Is there a standard procedure to go trough the mail/twitter/IRC/etc. channels? We were thinking of adding documentation (README of the repo + README of the images in the DockerHub + comments in the respective Dockerfiles) and writing a blog post. Is there something else?

As the documentation for these image is scarse, it is hard to evaluate the impact. If you have any knowledge on how it is being used (outside the Jenkins project's infra.), could you share it to help us?


Thanks in advance!

Damien DUPORTAL




--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/e06fb690-dd0c-4e00-89aa-6218634fd885n%40googlegroups.com.