colima

colima copied to clipboard

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: ba1be00e9aec47f2c1ffdacfb7e428e465f0b58a

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

• [ ] macOS Intel <= 13 (Ventura)
• [ ] macOS Intel >= 14 (Sonoma)
• [ ] Apple Silicon <= 13 (Ventura)
• [X] Apple Silicon >= 14 (Sonoma)
• [ ] Linux

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

1. colima start --vm-type vz --runtime containerd --cpu 2 test
2. colima status

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:///Users/testing/.colima/default/docker.sock

I am having the same issue. Until this is resolved, it is still possible to talk to docker via SSH:

docker context create colima-ssh --docker "host=ssh://colima"

~~same here but im using an old macbook with osx 11, docker wont install so i have to use containerd~~ edit: ignore me i can indeed run colima with docker and it works perfectly fine!

user@Users-MacBook-Pro ~ % colima version
colima version 0.6.8
git commit: 9b0809d0ed9ad3ff1e57c405f27324e6298ca04f

runtime: containerd
arch: x86_64
client: v1.7.3
server: 1.6.28
user@Users-MacBook-Pro ~ % colima status -e
INFO[0000] colima is running using QEMU                 
INFO[0000] arch: x86_64                                 
INFO[0000] runtime: containerd                          
INFO[0000] mountType: sshfs                             
INFO[0000] cpu: 2                                       
INFO[0000] mem: 2GiB                                    
INFO[0000] disk: 60GiB                                  
user@Users-MacBook-Pro ~ 

Same issue here with 0.6.9

Same issue here with 0.6.9, I suspect the issue occurs when using containerd + vz vm on mac os m1

Same issue: m3 macos, colima 0.6.10

This is actually the expected behaviour for containerd runtime. Do you still want to keep using docker for containerd runtime?

This is actually the expected behaviour for containerd runtime. Do you still want to keep using docker for containerd runtime?

Yes. If I'm using the docker runtime and some kubernetes, docker is full of the kubernetes containers, making it a bit hard to work with. And vz is necessary for virtiofs.