-
-
Notifications
You must be signed in to change notification settings - Fork 402
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
Python Docker SDK cannot create client from_env #468
Comments
Have you tried specifying the
|
The decision to not override default Docker settings but instead utilise contexts and a different socket is to make it easy for users to try out Colima without breaking their existing workflow. |
Thanks for the fast reply! The issue is fixed when I set this and the reason for using contexts makes a lot of sense. It looks like we'll need to update our tooling to check for both the default location as well as colima default location depending on what our users are using. Is there a potential future where you allow users the option to force override the default docker settings instead? This is the route we'd likely prefer if we asked our users to make the switch. Overall I've been trialing this workflow for the last few weeks and absolutely love it! Thanks for some great software 😄 |
This has been requested a few times now and will be prioritised for the next release. |
FYI, the command to override the default socket can be found in the FAQ.
|
I'm happy for you to close this with whichever state you think is most appropriate. Thank you again for the information provided. |
Thanks @abiosoft the symlink solves this. |
Neither of these fixes appear to be helping for Apple M2 Pro, colima 0.6.7, docker 24.0.7, and the |
Description
After switching from Docker Desktop to Colima, tooling written in Python which creates a Docker client using from_env() fails with the following error:
Version
Colima Version: 0.4.6
Lima Version: 0.13.0
Qemu Version: 7.1.0
Operating System
Reproduction Steps
Expected behaviour
Client is an instantiated Docker client object.
Additional context
I understand that this is probably not your concern given it is the official Docker Engine SDK that is breaking.
However, given Colima is designed to be an alternative way of running Docker on your workstation it would be great to have a workaround so it can continue to work as a drop-in replacement for Docker Desktop.
The text was updated successfully, but these errors were encountered: