-
Notifications
You must be signed in to change notification settings - Fork 214
Docker connection failure #1114
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
Comments
This is a problem with Docker Tooling 5.18.0, not CDT. This release updates docker-client to 9.0 and there is a bug preventing communication with the docker connection. A work-around is to uninstall the Docker Tooling feature and reinstall the previous version from: https://download.eclipse.org/update-docker-5.17.0. A new issue has been opened against Linux Tools: eclipse-linuxtools/org.eclipse.linuxtools#461 |
Thank you for the quick response |
The problem was determined to be docker-client 9.0 not being able to work with httpclient5. A new version of docker-client has been made (9.0.3) which uses httpclient 4 and there is a maintenance release of Docker Tooling (5.18.1) which has just been made available through the https://download.eclipse.org/linuxtools/update-docker site. This site should be already be configured as part of the EPP and just needs to be enabled for an update to occur. |
Tested, works. Thank you |
Describe the bug
Unable to access docker. No images or containers are shown. Build in docker image not possible,
To Reproduce
Start eclipse 2025/03 binary, create new workspace. Window -> Show View ->Other -> Docker -> Docker Images. No docker images are shown, despite many do exist and Eclipse 2024/12 does show them.
In eclipse2025-workspace/.metadata/.log:
!ENTRY org.eclipse.linuxtools.docker.core 1 0 2025-03-12 19:35:16.919
!MESSAGE Failed to ping the Docker daemon for connection 'unix:///var/run/docker.sock'
Expected behavior
Docker should work and the images should show up.
Screenshots
Eclipse 2025/03:
Eclipse 2024/12:
Version Information (please complete the following information):
The text was updated successfully, but these errors were encountered: