colima: Colima is not able to access local network connections after mac update
Description
Colima containers are not able to access the local network.
Possible cause: After recent macos updates, local network access for applications must be specifically enabled via System Settings. (Privacy and Security -> Local Network) I had to explicitly enable it for “Docker” however there is Calima doesn’t appear in the list of options to be enabled.
Version
colima version && limactl --version && qemu-img --version
colima version 0.7.5
git commit: 1588c066b9ab9dae8205ef265929c7eb43dca473
runtime: docker
arch: aarch64
client: v27.3.1
server: v27.1.1
limactl version 0.23.2
qemu-img version 9.1.0
Copyright (c) 2003-2024 Fabrice Bellard and the QEMU Project developers
Operating System
- macOS Intel <= 13 (Ventura)
- macOS Intel >= 14 (Sonoma)
- Apple Silicon <= 13 (Ventura)
- Apple Silicon >= 14 (Sonoma)
- Linux
Output of 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/xxxx/.colima/default/docker.sock
Reproduction Steps
- Run any container
- ping any computer on the local network
Expected behaviour
The local computer should be able to be reached by the container
Additional context
No response
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 10
- Comments: 16 (4 by maintainers)
I think we’ve got enough confirmations, would go ahead with the fix.
just for history, if anyone will face something similar, in my case, on fresh install I did:
later, realized that I need
--network-addressso tried:but it did not worked out 🤔
to fix this - make sure to at start from scratch by running:
for me
colima deletewas the missing piece, because stop, start won’t change those settings created on initial setupjust in case want to leave it here for future newcomers like me 🙂
Can you share the output of
colima ssh -- ip routeafter starting Colima with network address enabled?You should get something like the following
What happens if you delete the entry for the network address?
I see the above various timeouts connecting to a private Artifactory instance over VPN, on Mac OS 15.1. There were no issues prior to the Sequioa upgrade.
network.address: trueandnetwork.dns: [ <my internal DNS> ]unfortunately don’t improve anything. Using Docker Desktop instead of Colima does work, so my Artifactory instance and other networking are fine.And unlike the OP, Colima does appear in my System Settings → Privacy & Security → Local Network, and I have given it access. I also added & enabled it under Developer Tools (which seemed to be required for Docker Desktop, FWIW) and Full Disk Access to no effect. A complete reinstall of Colima including the removal of
~/.colima/also made no difference.I met the similar problem. I couldn’t push docker image to a registry in a local network by IP address. The workaround for me is setting
network.addresstotruein~/.colima/default/colima.yamlApple Silicon (M1): Sequoia 15.1
Also have this issue. Waiting for the fix. thanks
This fixes the issue as a workaround - I can still reach colima from my host with network-address and pulling images in colima from the Registry behind VPN works.
I have a similar issue after upgrading to Sequoia 15.1. Pulling images from a registry behind a VPN does not work anymore with colima flag
--network-address.Error message is similar to the previous poster, e.g.
net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers).However, if
network-addressflag is not set, pulling works fine.Reinstalling colima, using dev version, deleting profiles and colima/lima related files did not help. For me, colima does not apppear under System Settings → Privacy & Security → Local Network.
Operating System is
15.1 (24B83)on Intel Mac.