Containers on Apple Silicon with emulated x86 are not reachable from outside about colima HOT 11 OPEN

Thanks for creating this issue. I've been facing this issue on M3 chip Mac and after hours of start/stop cycle I downgraded colima as well.

from colima.

I now downgraded to Colima 0.5.6 - the only option that is obviously missing is --vm-type=vz-rosetta - but after this downgrade, everything is just working fine. :( So there must be an issue in the 0.6.x branch of some sort.

from colima.

Here are some other related issues:
#962
#801
#897

All of those have the same or at least a seemingly identical problem. Some said, they fixed it disabling ipv6, which did nothing for me, others suggest restarting the Mac, which I did not try because I wanted to find the root cause and downgraded to an older version of Colima instead, which was successful on the first try.

from colima.

same issue here with emulated x86_64 on M1 Mac. disabling IPv6 did not help.

from colima.

I can confirm that using --profile instead of --arch works, the address is listed as well under colima list

ie:
colima start --profile x86_64 --vm-type=vz --vz-rosetta --cpu 8 --memory 8 --disk 10 --network-address

from colima.

I can confirm that using --profile instead of --arch works, the address is listed as well under colima list

ie: colima start --profile x86_64 --vm-type=vz --vz-rosetta --cpu 8 --memory 8 --disk 10 --network-address

This is not possible, simply because --profile is just giving the thing a different name, it has nothing to do with --arch. I don't know why you think this is the solution, but no, it isn't. Naming something "x86_64" does not make it emulate this architecture at all. Maybe that's why you think it is working?

from colima.

Just updated from v0.6.7 to v0.6.8 and I'm facing the same problem.
It's weired but skipping --vm-type=vz option works for me (Ofcourse I prefer to use it though)

% colima start amd64 --arch x86_64                          
INFO[0000] starting colima [profile=amd64]              
INFO[0000] runtime: docker                              
INFO[0000] creating and starting ...                     context=vm
INFO[0075] provisioning ...                              context=docker
INFO[0076] starting ...                                  context=docker
INFO[0147] done                                         

% colima start amd64-r --arch x86_64 --vm-type=vz --vz-rosetta
INFO[0000] starting colima [profile=amd64-r]            
INFO[0000] runtime: docker                              
INFO[0000] creating and starting ...                     context=vm
> [hostagent] Forwarding "/run/lima-guestagent.sock" (guest) to "/Users/kento/.colima/_lima/colima-amd64-r/ga.sock" (host)
> [hostagent] connection to the guest agent was closed unexpectedlydial unix /Users/kento/.colima/_lima/colima-amd64-r/ga.sock: connect: no such file or directory
> [hostagent] The final requirement 1 of 1 is satisfied
> [guest agent does not seem to be running; port forwards will not work]
> DEGRADED. The VM seems running, but file sharing and port forwarding may not work. (hint: see "/Users/kento/.colima/_lima/colima-amd64-r/ha.stderr.log")
> degraded, status={Running:true Degraded:true Exiting:false Errors:[guest agent does not seem to be running; port forwards will not work] SSHLocalPort:50227}
FATA[0124] error starting vm: error at 'creating and starting': exit status 1 

@ M2, Ventura 13

from colima.

I can confirm that using --profile instead of --arch works, the address is listed as well under colima list
ie: colima start --profile x86_64 --vm-type=vz --vz-rosetta --cpu 8 --memory 8 --disk 10 --network-address

This is not possible, simply because --profile is just giving the thing a different name, it has nothing to do with --arch. I don't know why you think this is the solution, but no, it isn't. Naming something "x86_64" does not make it emulate this architecture at all. Maybe that's why you think it is working?

I just realizes this, yes. The address was exposed but not emulating.

from colima.