Connection reset by peer when running pip in a Colima powered Docker Container #577
Comments
|
@Ponsaille does the issue go away after a Colima restart? Also, can you can try |
|
@abiosoft using --network-driver slirp is working perfectly. I think we can close the issue. Thank you! Out of curiosity, would you have any resource for me to understand how using slirp made this work? |
|
For QEMU, Colima has two options for the network. Slirp is the default QEMU user-mode network while GVProxy is an alternative. It used to be only slirp in Colima but complains from users led to the trial of gvproxy and it turned out positive. Neither has been perfect so far but judging from issues reported by users, gvproxy seems to work for most people and is thereby made the default. |
|
Was also running into this on macOS Intel 13.2 - network dropping both in VM on host and eventually coming back. The |
|
@abiosoft using --network-driver slirp also worked for me, same issue but on macOS M1 >= 13 (Ventura). Thanks. |
Same here, if the mac uses intel, it works perfect with macOS 11 (Big Sur) but produce this error both with macOS 12 and 13 (Monterey and Ventura) Changing the network-driver do not solve the issue. Have you Dacort find a solution? |
|
@marino-serna No, I haven't. :\ I actually just had my entire VM freeze when I was trying to pull a new docker image. Things had actually been working pretty for me for a while, so not sure what happened. Here's my versions/status. |
* 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
Most of the time colima works perfectly and thank you for that.
However I keep coming across an error when I use pip (python's package manager) to install dependencies. After a time it outputs this error or something similar:
This happens only when using it from colima. I have tried on Ubuntu and this issue has never appeared.
I have tried a large number of fixes that where recommended online including setting the DNS of colima to 8.8.8.8 or installing the python package pyopenssl. Installing the packages directly in the alpine vm also seam to work.
I have not been able to find any differentiating factor so this is why I am opening the issue here. I hope you will be able to help me.
Version
Colima Version:
colima version 0.5.2
git commit: 6b5b6fe
runtime: docker
arch: x86_64
client: v20.10.19
server: v20.10.20
Lima Version: 0.14.2
Qemu Version: 7.2.0
Operating System
Output of
colima statusINFO[0000] colima is running using QEMU
INFO[0000] arch: x86_64
INFO[0000] runtime: docker
INFO[0000] mountType: sshfs
INFO[0000] socket: unix:///Users/ponsaijj/.colima/default/docker.sock
Reproduction Steps
Example of requirements.txt on which it has failed:
Dockerfile:
Expected behaviour
Packages installation should go through the end.
Additional context
No response
The text was updated successfully, but these errors were encountered: