-
-
Notifications
You must be signed in to change notification settings - Fork 389
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 still crashing under network load #603
Comments
I believe this is specific to the vz driver and related to this issue lima-vm/lima#1200. I will try to set out some time to troubleshoot the network and probably find an alternative network for the vz driver. |
I am facing the same issue when pulling large docker containers. |
just had the same issue. doing a docker pull / composer install after using scp to retrieve files on a docker volume inside a container. Afterwards colima was nearly useless as starting the instace took forever due to #690 and also composer install never seemed to finish anymore afterwards. but as mentioned by @abiosoft it is probably a lima and not a colima issue. |
@AndreasA are you using VZ or QEMU? |
@abiosoft I am using VZ. so I guess it is probably the lima issue? |
I'm having the exact same issue when using a Note that this happens only when running inside of a container, building seems to work fine and downloads could be anything from a package to a single file. I haven't been able to determine the exact cause of this. I attributed it to bind mounts and unpacking a file containing too many files (Using docker volumes seems to work fine) but I don't know anymore |
* build: Lock GitHub runners' OS This was motivated by our macOS jobs failing [2] because colima is missing. It looks like this is because the latest versions of the macOS runner no longer have colima installed by default [1]. colima is now explicitly installed. [1] actions/runner-images#6216 [2] `/Users/runner/work/_temp/f19ffbff-27a9-4fc7-80b6-97791d2de141.sh: line 9: colima: command not found` * build: Lock Colima * build: Move macOS Docker installation to script * build: Move macOS libomp activation to script * build: Use latest Colima The > 0.6.0 releases actually fix the issue we have linked [1][2][3]. [1] abiosoft/colima#577 [2] https://github.com/jesse-c/MLServer/blob/c3acd60995a72141027eff506e4fd330fe824179/hack/install-docker-macos.sh#L18-L20 [3] > Switch to new user-v2 network. Fixes abiosoft/colima#648, abiosoft/colima#603, abiosoft/colima#577, abiosoft/colima#779, abiosoft/colima#137, abiosoft/colima#740.
Description
My lima VM crashes as soon as network activity gets a little high (such as a Sabnzbd download starting).
Version
Colima Version: 0.5.0 (also tried with HEAD)
Lima Version: 0.14.2
Qemu Version:
Operating System
Output of
colima status
No output. The command hangs forever unless I run
killall limactl
Reproduction Steps
Expected behaviour
VM should be able to sustain network activity under some load.
Additional context
My Colima command:
I tried slirp and gvproxy for the network driver but it doesn't seem to make much of a difference.
Interesting to note, Docker Desktop for Mac had similar issues but they seem to have been fixed in version 4.16 (no more crashes for me since then): docker/for-mac#6530
The text was updated successfully, but these errors were encountered: