Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
DOCKER_HOST-strategy in class isDockerWorking.java excludes expected "unix:"-path where it should include "unix:" - broken.
See original GitHub issueDescribe the bug
In the file IsDockerWorking.java. line 129 -see https://github.com/quarkusio/quarkus/blob/main/core/deployment/src/main/java/io/quarkus/deployment/IsDockerWorking.java#L129
the check for the DOCKER_HOST-variable is negatated. However, setting the DOCKER_HOST variable to a unix socket usually involves a path like “unix:\\the\path\to\socket”. This is also clearly mentioned and recommened in your documentation -> https://quarkus.io/guides/podman#setting-docker_host-on-linux. The negation should most likely be removed so that the logic it now hides can run correctly (connection to the “unix:” socket in the DOCKER_HOST-env.
Expected behavior
It should find a DOCKER_HOST-path (according to practices, according to your documentation linked in descrioption starting with unix:\\the-path-to-the-socket.
Actual behavior
It instead excludes DOCKER_HOST paths starting with “unix:” due to starting with neg !.
How to Reproduce?
Set a DOCKER_HOST starting with “unix:\” for example as per docu, qurkus will fail finding it and connecting to it . https://quarkus.io/guides/podman#setting-docker_host-on-linux
Output of uname -a or ver
No response
Output of java -version
17
GraalVM version (if different from Java)
No response
Quarkus version or git rev
2.13.4
Build tool (ie. output of mvnw --version or gradlew --version)
No response
Additional information
No response
Issue Analytics
- State:
- Created 10 months ago
- Comments:9 (9 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I created https://github.com/quarkusio/quarkus/pull/29562 to take care of this.
Thanks @Sanne . Heads up, Another note is that the current documentation example mentioned above for setting DOCKER_HOST is also pointing to a podman socket path that might differ on different setups of linuxes. To see which is the correct path for your podman instance see
podman info | grep -A2 'remote'and you should get roughly like
back which shows the correct podman socket path - ie set DOCKER_HOST=unix://THE_ABOVE_PATH. (Also exists should be true.)