-
Notifications
You must be signed in to change notification settings - Fork 323
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
java.lang.ClassNotFoundException: com.github.dockerjava.netty.WebTarget on 'Test Connection' #782
Comments
Confirmed that downgrading the Docker-API plugin from 3.1.5 to 3.0.14 fixes the problem...should I close the issue, or is this still a Docker plugin issue since it relies on it? |
This plugin can only specify a minimum version of plugins it depends on; it can't say "don't use > v1.2.3" so there's no code changes possible that'd fix it here. This needs fixing in the docker Java API plugin (and ASAP). |
It looks like that project has bug reports disabled... |
Is there some way to contact Eric Citaire directly? |
Hmm... @ericcitaire did you get access to docker-java-api in the end? Are you aware of this unwanted side effect? |
This is probably all to do with PR #777 here so, yes, I'm fairly sure Eric will notice this. |
FYI it's now 1am where I am (UK) and I really should be going to sleep now ... but I'll check my email etc tomorrow morning. |
That would be most appreciated. I'm creating a Jenkins-Docker course for Pluralsight, and that will get me unblocked. If you guys have anything you wish people knew about this stuff, let me know and I'll include it. |
Any ETA for release of fix for this issue. Its blocking me. ASAP release would be appreciated. |
Hi all. Thank you for reporting this. As stated by @pjdarton, there's no way to specify a maximum version in plugin dependencies.
I created a PR (#777) to upgrade In the meantime, the only thing I can suggest you is to downgrade to |
Docker plugin 1.2.0 is available; that works with docker-java-api-plugin version 3.1.5 (but not with version 3.0.14) |
Verified - this is working correctly now - thanks for fixing this so quickly. |
I just released docker-java-api-plugin 3.1.5.1, with an incompatibility warning (see screenshot below). I hope this will limit the damage for those who didn't update the plugin yet. Sorry for the inconvenience and thanks a lot to @pjdarton for fixing my mistake. |
Not fixed.
Repeating those messages every 10s and nothing happens... The job is still stuck. |
I had the same issue as @roman-vynar when upgrading the two plugins and have also had to revert to the previous versions. |
This is not the same issue. Can you create a separate issue please? Also, it would be great to tell us how to reproduce this, because I don't have this behavior. Thanks. |
Not the same but directly related. I am just building a job pointed to the jenkins cloud template which therefore is pointed to a local docker socket. Nothing special. The job is stuck in the queue and not progressing. The behaviour is described above and one other user confirmed. |
I think this is the same issue ^^ |
@roman-vynar @grit96 What you're reporting is a new issue. It's probably got the same underlying trigger (the change to the docker-java-api-plugin or, more specifically, it's change from docker-java version 3.0.14 to version 3.1.5), but the solution will be very different. For anyone else watching, or anyone in future finding this issue after encountering other issues seemingly caused by the upgrade from docker-java-api-plugin 3.0.14 to 3.1.5, please raise a new issue and include a mention of this one (just use the text |
I'm using latest version of the plugin - 1.1.9, upgraded as part of the new Jenkins LTS (2.222.1). When attempting to configure a new Docker cloud, I'm attempting to test the connection to the host (which I have verified is running with a containers/json call in the browser), and I receive this error:
I believe this actually may be due to a problem in the Docker-API plug-in, which has changed with the LTS as well. This all worked perfectly when Jenkins LTS was 2.204.6:.
The text was updated successfully, but these errors were encountered: