foxylion / docker-jenkins Goto Github PK

I bring up a slave via ssh-agent docker and setup some jobs running on it. But the problem is the job running on this docker slave is isolated within the docker container, is there a good approach to expose the host resouce(the libs commands fs) to this jenkins slave running by ssh docker agent?

BTW, I source your example that running docker to mount the docker socket file into agent container, what is the reason you did this?

Thanks for putting this together, it's an incredible resource! But...

I started off trying to set up my own images riff'ing off your your example, but could not get it to work. So I cloned your repository, cd'ed into docker-images/master and ran docker build .

Then I ran:

docker run --name jenkins -p 8080:8080 -p 50000:50000 -v ~/tmp/blah:/var/jenkins_home e2a95803c8ab

where e2a95803c8ab is the id of the image I just built.

I am unable to log in as the user admin with the password admin, I get the error message:

Invalid login information. Please try again. 
Try again

I also just tried to run foxylion/jenkins like so:

docker run --name jenkins -p 8080:8080 -p 50000:50000 -v ~/tmp/blah:/var/jenkins_home foxylion/jenkins

and have the same problem.

After running the container there there is a file in ~/tmp/blah called users/admin/config.xml that contains this (amongst more):

    <hudson.security.HudsonPrivateSecurityRealm_-Details>
      <passwordHash>#jbcrypt:$2a$10$NcvhiPxOKBd4SuwRxTXVnufLhrMhV6YTLQzZCn88iKy9vmVm3VYju</passwordHash>
    </hudson.security.HudsonPrivateSecurityRealm_-Details>

so it seems as if something is nearly there.

I suspect (Murphy requires!) that I'm doing something silly, but I can find it.

I don't see any logging info in the console or anywhere in jenkins_home. Is there somewhere I can start digging?

In Readme you have said:

"Note: Using a JNLP slave does not provide any encryption when communicating with the master. In an untrusted network this is not recommended. Use instead the ssh slave image."

But seems it's not true for now https://i.imgur.com/yHWlLn3.png. Am I correct?

Sorry, but for me the build fails with error: "make: *** No rule to make target `vagrant'. Stop."

In docker-jenkins/docker-images/master/default-user.groovy,

the line

jenkins.getAuthorizationStrategy().add(Jenkins.ADMINISTER, 'admin')

uses the literal value 'admin' to set the user account to ADMINISTER privilege. It seems like this should instead be

jenkins.getAuthorizationStrategy().add(Jenkins.ADMINISTER, env.JENKINS_USER)

so the newly created account has admin privileges. As is, if the env variable JENKINS_USER isn't 'admin' ( say 'jenkins' instead ) the code doesn't work.

Hey

This docker is running successfully on Localhost without any errors, but when I configured it on an online server, and I go to the URL so it's showing 502 - bad gateway.
Could you help me to solve this issue?