colima: option --network-address does not expose internal ip address
Description
Starting colima with --network-address, or setting address: true in the config file, does not expose internal IP address of the docker host. colima list outputs an empty value for the ADDRESS column:
➜ ~ colima list
PROFILE STATUS ARCH CPUS MEMORY DISK RUNTIME ADDRESS
default Running aarch64 4 4GiB 100GiB docker
Version
Colima Version: 0.4.6 Lima Version: 0.12.0 Qemu Version: Stable 7.1.0
Operating System
- macOS Intel
- macOS M1
- Linux
Reproduction Steps
- colima start --network-address
- <wait until colima started>
- colima list. The address field is empty
Expected behaviour
colima list should apparently show an ip address that can be used to access anything listening within the docker container
Additional context
No response
About this issue
- Original URL
- State: open
- Created 4 years ago
- Reactions: 12
- Comments: 53 (8 by maintainers)
Hi, I have similar problem:
I’ve tried starting
colimawith:but my
ADDRESScolumn is empty.colima lsoutput:Any advice what am I missing?
Hello I share with you a shell script to fix this issue and manually expose the IP. Please let me know if it works for you.
Try downgrading the colima version from
0.6.7to0.6.6, that worked for me onApple M3 ProThat’s strange. If you upgraded from a version < 0.4.0, you should
colima deleteand start afresh.Can you stop colima and clear the following files, then try again?
If it still fails, kindly run with
--very-verboseflag and share the output.Thanks.
Got
Cannot find device "col0"When typingip addron the vm I see the following devicesMy mac: M3 chip, Sonoma 14.3.1 (23D60)
This worked for me after a reboot.
MacOS Sonoma Colima 0.5.5
finally got it worked by deleting the existing colima.
most probably, i did create the colima without specify the
--archand--vm-typethus it’s failing to retrieve the ip address of the docker host on Mac.Can you try with
--network-driver slirp?I encountered this suddenly on macOS 14 with the system firewall enabled.
Disabling the system firewall, while a somewhat radical solution that needs to be considered well, helped.
Oddly, it used to work with the system firewall being enabled. The only conscious change in the last days was installing and using the AWS Client VPN. I wonder if that maybe messed with things… VPN was disabled while I tried colima, by the way.
I wonder if there is any program I could whitelist in the firewall settings?
Update: Whitelisting
bootpdas per https://github.com/abiosoft/colima/issues/449#issuecomment-1989842823 did the trick. Still not sure why it suddenly stopped working…@RobertoMD : See if specifying a specific firewall rule for
bootpdso the VM is allowed to get an IPv4 address via DHCP helps: https://github.com/abiosoft/colima/issues/458#issuecomment-1989839779This is working for me… thanks @afettahghazi
MacOS Sonoma (M1) Colima 0.5.6
@afganhalbana so i had colima working, then i upgraded my mac to Sonoma and then colima isnt working. I have tried your suggestion above and it is still not working
I had the same issue, but while using the
vzvm-type. Was able to resolve the issue with rebooting MacOS.@abiosoft , It DOES work with the --network-driver slirp option. I’ll use this option from now on. Thanks!