Comments on: How to run Jenkins with docker?

By: Emil

Emil — Sat, 25 May 2019 08:58:40 +0000

Hi!

What do you mean when you say that you “have to run the Jenkins in docker with different user”? With a different user than the default one in the host system (e.g. not as user “ubuntu” with the UID 1000)? Or you have to change user “jenkins” in the image to another one?

Anyway, independently from that, when you set up your Jenkins in docker, you should be able to run any command in the build step (I assume that you mean some shell scripts as a build step) without any problem and without necessity of adding some “su USER” or something like that. All build steps should “inherit” the user from the container. Like for normall installation.

By: Pooja Kataria

Pooja Kataria — Fri, 24 May 2019 11:01:53 +0000

Hi,

I have to run the Jenkins in docker with different user .So that when i add any command in the Build Step in the New item it should use that user ?
Can you help me how can i achieve this ?

By: Emil

Emil — Fri, 16 Nov 2018 10:56:13 +0000

In reply to Dali.

Hi, Dali!

Thanks for feedback! Yes, you’re right, –rm it’s very useful when you use a standard docker command. I’d prefer to use docker-compose on a daily basis work, so I forgot to add this option to my post. But I’ll fix that asap! 🙂

By: Dali

Dali — Thu, 15 Nov 2018 10:21:32 +0000

Thanks for sharing,
I somehow followed your howto to implement my testing jenkins to not to compromise our corporate.
adding my 50cents : add –rm flag to the run command to not to get this error after stoping and attempting to start again :
docker: Error response from daemon: Conflict. The container name “/myjenkins” is already in use by container 3d4b6c645b5029087893ea4b7846573e727432dc4577851960efc39d3cca493c. You have to remove (or rename) that container to be able to reuse that name..
so final command will be :
# docker run -d -v /var/jenkins_home:/var/jenkins_home:z -p 8080:8080 -p 50000:50000 –rm –name myjenkins jenkins/jenkins:lts

All the best

By: Emil

Emil — Mon, 10 Sep 2018 18:46:26 +0000

In reply to dragon788.

Hi, Dragon!

Thanks for your feedback! Yes, you’re right, it’s a very good idea to add docker volume to this article. And yes, it’s exactly that command. 🙂 I will try to update my article this week. Thank you very much! 🙂

By: dragon788

dragon788 — Mon, 10 Sep 2018 16:50:11 +0000

It might be worthwhile to update this to show using a Docker volume `docker volume create my_jenkins_home` instead of mapping in from the host and then `docker run -d my_jenkins_home:/var/jenkins_home …etc`. This should avoid the host/guest permissions issues while still allowing for persistence.

You also didn’t show the command you used to get into the container to get the initialAdminPassword. I believe it is something like `docker exec containerID cat /var/jenkins_home/secrets/initialAdminPassword`.