search

abiosoft / colima

Container runtimes on macOS (and Linux) with minimal setup
MIT License
18.85k stars 382 forks source link

SLIRP nw driver stops working quite often #678

Open gpsa opened 1 year ago

gpsa commented 1 year ago

Description

After having some issues with gvproxy, I was suggested to use SLIRP, however I've been noticing that, during the day, it stops working and all the mounting points crash, although I see that the VM is still accessible (colima ssh works). That's the same behaviour I noticed when using Lima directly, because I believe they use SLIRP by default. The solution right now is to restart colima every time it happens, but is there anything that can be done to tackle this issue at Colima's domain, or would that be something more about Lima or even QEMU?

Version

Colima Version: 0.5.4 Lima Version: 0.15.0 Qemu Version: 7.2.0

Operating System

Output of colima status

INFO[0000] colima is running using QEMU
INFO[0000] arch: x86_64
INFO[0000] runtime: docker
INFO[0000] mountType: sshfs
INFO[0000] socket: unix:///Users/user/.colima/default/docker.sock

Reproduction Steps

  1. colima start # keep working on your containers and wait...that will eventually happen

Expected behaviour

Mounting points to continue to work properly

Additional context

docker ps Cannot connect to the Docker daemon at unix:///Users/user/.colima/default/docker.sock. Is the docker daemon running?

colima ssh

ash: cd: line 0: can't cd to /Users/user/mysharedfolder: No such file or directory
FATA[0000] exit status 1
dheardal commented 1 year ago

Did you get anywhere with this? I am having the same issue

gpsa commented 1 year ago

Unfortunately not, still waiting for some help, although I believe this has more to do with lima / QEMU because something similar happens when I'm just running Lima alone.

fskaeh commented 1 year ago

Hi @abiosoft, if I'm not mistaken, I believe Lima's latest 0.16 release should help with this issue: https://github.com/lima-vm/lima/pull/1383 But we might need a small update on Colima's side to handle this new value user-v2 to replace slirp.

abiosoft commented 1 year ago

Hi @abiosoft, if I'm not mistaken, I believe Lima's latest 0.16 release should help with this issue: lima-vm/lima#1383 But we might need a small update on Colima's side to handle this new value user-v2 to replace slirp.

The main advantage of user-v2 is for vm-vm communications. e.g. a multi-node Kubernetes cluster or docker swarm.

github-nicolas-stadler commented 1 year ago

Hi @abiosoft, if I'm not mistaken, I believe Lima's latest 0.16 release should help with this issue: lima-vm/lima#1383 But we might need a small update on Colima's side to handle this new value user-v2 to replace slirp.

The main advantage of user-v2 is for vm-vm communications. e.g. a multi-node Kubernetes cluster or docker swarm.

Agreed, but as it stands VZ+Slirp is just broken (at least for me and some other people judging by the issues), so anything that lets us get rid of Slirp is very welcome.

abiosoft commented 1 year ago

Agreed, but as it stands VZ+Slirp is just broken (at least for me and some other people judging by the issues), so anything that lets us get rid of Slirp is very welcome.

user-v2 is being evaluated to see how best to integrate it in to Colima.