jenkins-docker | docker file for a jenkins docker image | Continuous Deployment library

You need to use http://161.61.222.16:30878/ from outside of the host which is running containers on. Port 5001 is just accessible inside the cluster with internal IP (9.5.52.28 is in your case). Whenever you expose your deployment, automatically (also you can define manually) one of the NodePort (by default between 30000 - 32767)assign to the service for external request.

For service details, you need to run the below command. The command output will give you NodePort and another details.

Where do you store plugins.txt file?

It should exist in the same folder with Dockerfile.

According to the Jenkins downloading-and-running-jenkins-in-docker documentation:

4. In order to execute Docker commands inside Jenkins nodes, download and run the docker:dind

Docker in Docker(dind) allows Docker engine to run as a Container inside Docker - which is the kind of inception that feels intuitive to do.

I just reproduced and just worked just fine for me with these commands(I also included --privileged in the launch options. Not sure if it is mandatory):

I don't use docker on windows, so sorry if this work-around is not useful !

You can make a .bat script that runs the command at startup ( task scheduler should have the option as you might want to wait for Docker to finish loading ).

Here is a level 0 tutorial that also shows how to setup a task at startup.

You are probably running Jenkins in a container. Jenkins container does not have python installed because it's not needed in order to run Jenkins, and containers by design only include the minimal necessary things.

Moreover, you are running your job on Jenkins master, so it runs in the same place as Jenkins (Jenkins container), so no python and no pip and no easy_install.

You should run your job somewhere where python and pip are installed. You may want to consider running the job in the python container, e.g. like this:

You also need to set the --prefix command on your jenkins installation. You can do this in the jenkins.xml config file or by altering your command line arguments to include --prefix=/jenkins.

The arguments can be seen at https://wiki.jenkins.io/display/JENKINS/Starting+and+Accessing+Jenkins

Thanks to @JoergS for some insight! The culprit in this case is: using alpine image as the docker base. So switching from jenkins/jenkins:2.131-alpine to jenkins/jenkins:2.131 solved the NodeJS plugin issue.

EDIT: i read the question as how to have production Jenkins maven builds avoid downloading artifacts by sharing the .m2 folder. The question is about getting a tutorial on running maven in a local docker instance to work. Not quite the same.

—-

Several solutions exist. Do not share/persist the .m2 folder, Maven is not thread safe (last time I really looked into this, might be fixed by now)

Simplest is to set up a Maven mirror repository (Nexus works well for this) and tell your docker Maven build to use that as a mirror.

Ugh. This was down to the way that I'd set up docker support on the slave container.

I'd used socat to provide a TCP server proxy. Instead, switched that out for a plain old docker.sock volume between host & container.