-
Notifications
You must be signed in to change notification settings - Fork 601
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
docker build using colima with lima v0.23.1 hangs #2556
Comments
Which command hangs? |
Sometimes |
Thanks for taking a look. The command that hangs is that That same command works fine when I downgrade lima back to v0.22.0, so its not firewall related. It's something that changed when upgrading to lima v0.23.1. |
Came here to search for just an issue like that. I have the same problem in a larger project using the container I have tried the docker command from this issue on my MacBook with an Intel processor and saw it hang too. Using the |
Might be related or not, really not sure, but sounds related, and certainly did not happen with 0.22.0. We've been seeing random hangs from running containers with 0.23.1. What happens is requests to http services running in containers just hang indefinitely. If I wait a min or so and try again, often it will start working properly. Downgrading lima to 0.22.0 makes the problem go away entirely. Started the colima VM with: This is on an M1 Pro macbook. Happy to provide any other debugging info that might be helpful. For reference, used this to downgrade since brew doesn't make it easy:
|
On my system, a |
@ns-dfarino Can you try with latest lima head it has gvisor-tap-vsock 0.7.5 ??
Gvisor-tap-vsock has a regression with 0.7.4. This is fixed in 0.7.5. containers/gvisor-tap-vsock#386 |
@balajiv113 very good! 4592e34 works correctly. |
I also checked to see if this fixes my problem and it does. Great stuff. |
This MR contains the following updates: | Package | Update | Change | |---|---|---| | [lima-vm/lima](https://github.com/lima-vm/lima) | patch | `v0.23.1` -> `v0.23.2` | MR created with the help of [el-capitano/tools/renovate-bot](https://gitlab.com/el-capitano/tools/renovate-bot). **Proposed changes to behavior should be submitted there as MRs.** --- ### Release Notes <details> <summary>lima-vm/lima (lima-vm/lima)</summary> ### [`v0.23.2`](https://github.com/lima-vm/lima/releases/tag/v0.23.2) [Compare Source](lima-vm/lima@v0.23.1...v0.23.2) #### Changes - Network: - Fixed a stability issue ([#​2556](lima-vm/lima#2556), [#​2561](lima-vm/lima#2561)) - Templates: - Updated to the latest revisions ([#​2556](lima-vm/lima#2556)) Full changes: https://github.com/lima-vm/lima/milestone/49?closed=1 #### Usage ```console [macOS]$ limactl create [macOS]$ limactl start ... INFO[0029] READY. Run `lima` to open the shell. [macOS]$ lima uname Linux ``` *** The binaries were built automatically on GitHub Actions. The build log is available for 90 days: https://github.com/lima-vm/lima/actions/runs/10610584784 The sha256sum of the SHA256SUMS file itself is `9183a5703205d331d89f4a62abdbbb377cb77f1f49f8171cfa722960d7174bf1` . *** Release manager: [@​AkihiroSuda](https://github.com/AkihiroSuda) </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever MR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this MR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this MR, check this box --- This MR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy40NDAuNyIsInVwZGF0ZWRJblZlciI6IjM3LjQ0MC43IiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJSZW5vdmF0ZSBCb3QiXX0=-->
Description
This command hangs indefinitely using lima v0.23.1:
This is not a problem when using the previous version of lima (v0.22.0).
Colima was started with:
System information:
The text was updated successfully, but these errors were encountered: