-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Fails under a Jakarta ecosystem #2203
Comments
Figured out this particular issue. Still have questions, but for posterity and so this code doesn't only exist on Twitter:
|
Hi @GregJohnStewart , would you share how you figured out the original issue? |
The original issue was due to JEE packaging changes, and the default connector(s) using the older packages (javax). By switching to the zero dependency connector, those libs aren't pulled in and works fine. I was only able to find that code example on a tweet, nothing in documentation. |
PTAL at https://github.com/docker-java/docker-java/blob/main/docs/getting_started.md#instantiating-a-dockerhttpclient and especially https://github.com/docker-java/docker-java/blob/main/docs/transports.md . Also note that the library will print a warning when the default (Jersey) transport is used (for backward compatibility) |
s/nothing on documentation/no code examples for zero dep/ As you point out the docs mention zero dep, but no actual examples. (At least a few months ago) The first link you posted was using the libs that incurred the wrath of Jakarta (a few months ago). If the libs have been updated to Jakarta since, great. |
Hello, I am trying to use this utility with Quarkus 3.x, which has made the swap over to the new(er) Jakarta EE top-level-package, as opposed to the Javax one. This results in the following errors, as javax implementations aren't available:
Are there plans to update to the new(er) packaging scheme? It should be a simple matter of find and replace all
javax
strings withjakarta
, unless something more advanced is going on.Edit:: I have since found the documentation on the transports. However, a couple things:
unix:///var/run/docker.sock
file, and the docs aren't super clear as to how to just go the simple route. (Looking to go the ZeroDep route)The text was updated successfully, but these errors were encountered: