colima
colima copied to clipboard
"colima ls -j" does not contain "address" field when running in "--arch x86_64" mode
Description
When running Colima on my M4 Macbook like this (took from here to get it working with Testcontainers):
colima start --network-address
This command:
colima ls -j
gives me:
{"name":"default","status":"Running","arch":"aarch64","cpus":2,"memory":2147483648,"disk":107374182400,"address":"192.168.205.3","runtime":"docker"}
But, if I want to use Colima in x86_64 mode (to get Oracle images working (which I need with Testcontainers for my integration tests)) and start it like this (first running colima stop and colima delete, of course):
colima start --arch x86_64 --network-address
then executing colima ls -j gives me:
{"name":"default","status":"Running","arch":"x86_64","cpus":2,"memory":2147483648,"disk":107374182400,"runtime":"docker"}
So, the address field is not there anymore.
P.S. colima version 0.8.1
Version
No response
Operating System
- [ ] macOS Intel <= 13 (Ventura)
- [ ] macOS Intel >= 14 (Sonoma)
- [ ] Apple Silicon <= 13 (Ventura)
- [x] Apple Silicon >= 14 (Sonoma)
- [ ] Linux
Output of colima status
When started with colima start --arch x86_64 --network-address:
colima status
INFO[0000] colima is running using macOS Virtualization.Framework
INFO[0000] arch: x86_64
INFO[0000] runtime: docker
INFO[0000] mountType: sshfs
INFO[0000] socket: unix:///Users/anatoliibalakiriev/.colima/default/docker.sock
When started with colima start --network-address:
colima status
INFO[0015] colima is running using macOS Virtualization.Framework
INFO[0015] arch: aarch64
INFO[0015] runtime: docker
INFO[0015] mountType: sshfs
INFO[0015] address: 192.168.205.3
INFO[0015] socket: unix:///Users/anatoliibalakiriev/.colima/default/docker.sock
Reproduction Steps
- Start Colima with this command:
colima start --arch x86_64 --network-address - Run
colima ls -jand check the output
Expected behaviour
field "address":"<some IP address>" must be present, but it's not.
Additional context
No response
Are there any updates on this? This has been running in the wild for a couple of months now. And it breaks our development process since it's a requirement for running testcontainres
@MrwanBaghdad I personally needed it to run an older version of Oracle DB (21, from here: https://hub.docker.com/r/gvenzl/oracle-xe) and fixed it by switching to the latest one (23, from here: https://hub.docker.com/r/gvenzl/oracle-free), which does support Apple's ARM M-chips natively.