-
-
Notifications
You must be signed in to change notification settings - Fork 365
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
Colima with containerd runtime not exposing docker.sock #958
Comments
I am having the same issue. Until this is resolved, it is still possible to talk to docker via SSH:
|
|
Same issue here with 0.6.9 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
I started colima with containerd runtime. I cannot connect to it with docker since it didn't expose a docker socket
When I performed the same with docker runtime, it works fine.
Version
colima version 0.6.7
git commit: ba1be00
runtime: docker
arch: aarch64
client: v24.0.7
server: v24.0.7
limactl version 0.19.1
qemu-img version 8.2.0
Copyright (c) 2003-2023 Fabrice Bellard and the QEMU Project developers
Operating System
Output of
colima status
INFO[0000] colima [profile=test] is running using macOS Virtualization.Framework
INFO[0000] arch: aarch64
INFO[0000] runtime: containerd
INFO[0000] mountType: virtiofs
Reproduction Steps
Expected behaviour
I expect colima to expose the docker.sock in the host OS and have it visible in colima status command, just like with docker runtime
Additional context
Sample output when using docker runtime
colima start --vm-type vz --runtime docker --cpu 2
colima status
INFO[0000] colima is running using macOS Virtualization.Framework
INFO[0000] arch: aarch64
INFO[0000] runtime: docker
INFO[0000] mountType: virtiofs
INFO[0000] socket: unix:https:///Users/testing/.colima/default/docker.sock
The text was updated successfully, but these errors were encountered: