-
Notifications
You must be signed in to change notification settings - Fork 322
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add some troubleshooting docs? #97
Comments
I had a suspicion that it was because I started up my server with the -P command instead of explicit port mappings, but that didn't work either.
|
Ok, looks like the port that's not working is 22 from the slave, from
|
In my continued attempt to get this to work I ran
So my presumption that the containers couldn't ssh into each other is out. What am I missing that is preventing Jenkins from connecting to these slaves? |
I found some more logs:
|
What version of the docker-plugin are you using? A bug in Docker 1.2.0 prevents docker-plugin 0.7 from working. A workaround is available in 0.8. |
I'm using version 0.7 of the Docker Plugin and Docker 1.2.0. And I'm using Jenkins 1.565.2. I don't see an update for 0.8 of the plugin? |
Ah I see I need jenkins updated to at least 1.580. I'll update and let you know what I see. |
Works great with latest Jenkins! Thanks. |
I have been having some trouble getting this plugin to work, but I don't see any common troubleshooting documentation I can turn to to figure out what's going wrong.
I have been able to get this plugin to successfully start my containers, but they are not getting used to execute jobs. I'm not sure why and I don't know where to begin to look.
I am seeing this on the mange jenkins page:
I'm not sure which port setting that is referring to, and here are the log details.
I am using the evarga/jenkins-slave container from docker hub, and I have the user jenkins:jenkins setup.
I am running the Jenkins server in a docker container as well using the image provided by the docker team: https://registry.hub.docker.com/_/jenkins/
I ran that container with
run -d -P --name jenkins-server --volumes-from jenkins-data jenkins:1.565
wherejenkins-data
is a data volume I have setup for the server.And here you can see that jenkins is spawning the containers:
The text was updated successfully, but these errors were encountered: