jenkinsci/docker

Jenkins Docker packaging and plugins

dduportal

@dduportal:matrix.org

[m]

it is using the default jenkins user: it's the default official image

but the COPY instructions in the Dockerfile is always executed as root, unless you add the flag --chown

My problem is solved by changing it to COPY --chown=jenkins:jenkins ./plugins.txt /usr/share/jenkins/ref/plugins.txt

and this is what I want to contribute to the documentation

dduportal

@dduportal:matrix.org

[m]

I'm still trying to understand why this file is read during the startup. I suppose that it's read by the entrypoint jenkins.sh or one of its sub-scripts

Tim Jacomb

@timja

ah sure

yes makes sense

Mark Waite

@MarkEWaite

I agree with @timja . That looks like there is a bug in the Docker image that it is not running as user 'jenkins' for the copy step. I've confirmed the same behavior with 2.277.1-jdk11

Same behavior in 2.263.1-jdk11. The copied plugins.txt file is owned by user root (in my case with permissions 0644)

dduportal

@dduportal:matrix.org

[m]

@MarkEWaite: in fact, this is the expected behavior :)

@MarkEWaite: as per https://docs.docker.com/engine/reference/builder/#copy:

Mark Waite

@MarkEWaite

Ah, once again, me learning more things about Docker. I assumed the COPY operation would be performed as the current user in the script.

1 reply

dduportal

@dduportal:matrix.org

[m]

All new files and directories are created with a UID and GID of 0, unless the optional --chown flag specifies a given username, groupname, or UID/GID combination to request specific ownership of the copied content

Let me open the PR for the Jenkins doc at first

Mark Waite

@MarkEWaite

Then the difference is somehow in the umask? My files are 0644 and yours are 0600

dduportal

@dduportal:matrix.org

[m]

yep, I'm not really sure about why this

(umask)

but for sure, this issue prevent the helm chart to work as expected (the casc and plugins config are not applied)

dduportal

@dduportal:matrix.org

[m]

https://github.com/jenkinsci/docker/pull/1097/files

DoofusCanadensis

@kenrachynski:matrix.org

[m]

trying to set up Jenkins on Docker with the ability to use another docker host following the documentation

just realized that the documentation is assuming that you are going to run jobs on the controller

which is completely counter to the rest of the documentation saying "don't run jobs on the controller"

DoofusCanadensis

@kenrachynski:matrix.org

[m]

well, with the help of a digitalavenue.dev tutorial I was able to figure things out

still getting burned by a lack of arm64 image, though

Mark Waite

@MarkEWaite

@kenrachynski:matrix.org we discussed arm64 further in last week's platform SIG meeting. If you're interested in helping, we're very interested in having the help. Were you looking for an arm64 image for the controller or an arm64 image for an agent or both? Are you running arm64 in a Kubernetes cluster environment ?

Yes, the tutorials (Maven, NodeJS, and Python) take shortcuts to reduce steps and increase the chances of success for the person running the tutorial. The shortcuts include:

Docker in Docker using dind
Local directory mounted as /home/GitHub containing local repositories

We still have too many readers that are unable to successfully complete the tutorials, even with shortcuts. Happy to have additions and improvements.

DoofusCanadensis

@kenrachynski:matrix.org

[m]

@MarkEWaite: Thank you for the update. I'll try to pay more attention to the platform meetings from now on.

In this particular case, I was only looking for an agent, but I'm likely to want controller as well in the future. I am not running Kubernetes yet as I'm prototyping pure Docker solutions for home and work labs. I do expect to get to k8s eventually, though.

OH. I looked at the Java with Maven tutorial and see that the Installing Jenkins with Docker page took everything up to Fork and Clone Sample Repository for its own page

That install page makes more sense when it's part of this tutorial

Thank you for the pointer

DoofusCanadensis

@kenrachynski:matrix.org

[m]

As it is, I have three docker clouds setup now: one using the host that the controller is running on, one using the dind container, and one on my raspberry pi. I rebuilt the jenkins/agent:latest-jdk11 container directly on arm64, but I haven't been able to get it to launch properly yet.

dduportal

@dduportal:matrix.org

[m]

Hello DoofusCanadensis ! If you are interested, you might want to look at Docker buildx capacities, in particular for automating the "QEMU setup" on your amd64 machine, to allow better performances compared to a Pi

DoofusCanadensis

@kenrachynski:matrix.org

[m]

that's an interesting idea, but I'm working with the pi until I get an Apple M1 system to run. performance is currently secondary to getting the thing working

qspors

@qspors

Good morning. Where can I get complete guide for build own jenkins-slave docker image, I need to use amz linux, I'm trying to build image, unfortunately it not works properly. I tried to modify official jenkins/inbound-agent based on debian, this is works good, but debian is not appropriate for me. Thank you.

DoofusCanadensis

@kenrachynski:matrix.org

[m]

curious as to what makes it inappropriate

in any case, the source to that image is at https://github.com/jenkinsci/docker-agent

qspors

@qspors

I have solid requirements, I need jenkins-slave based on AMZ2, I can't move from this reqs, yeah this is problem and headache

DoofusCanadensis

@kenrachynski:matrix.org

[m]

fork that repo and modify... that's the base to all Jenkins agent images

qspors

@qspors

Thank you guys, Thank you @kenrachynski:matrix.org , Image deployed and works good.

halkeye

@halkeye:g4v.dev

[m]

I think there are newer images with centos tags though, I suspect not jenkins slave since slave has been depricated since 2.0, so it probably got stopped updating at some point

DoofusCanadensis

@kenrachynski:matrix.org

[m]

yeah, I didn't even address the 'slave' nomenclature

Tim Jacomb

@timja

jenkinsci/docker#1108 & jenkinsci/docker#1109

halkeye

@halkeye:g4v.dev

[m]

@timja: for the second one, wouldn't that mean this channel becomes a support channel for any docker image related issues?

DoofusCanadensis