below an output of some commands as you can see v1 vs v2 are two different executables. I can confirm that I'm not running Rosetta (nor do I want to). I'm not sure what caused that setting to be turned off somehow and why a fresh install today also has Docker Compose V2 off by default. It seems that Compose V2 has been around for quite a while now, and it must have been on by default in the past because I've never had this problem until today. But out of curiosity, I completely uninstalled Docker Desktop and reinstalled it again, and "Use Docker Compose V2" was off by default. If it's off, it leaves it off, if it's on, it leaves it on. Interestingly, resetting factory settings seems to ignore the "Use Docker Compose V2" setting. I'm not sure how generic is that issue, but docker-compose was working fine for the past weeks and all of a sudden stopped working with this CPU error.īy random trial and error I solved it by ticking "Use Docker Compose V2" in general preferences. Install Docker 4.6.0 on a M1 Mac and run docker-compose. Not sure what's that VM issue here but seems unrelated? I can use Docker no problem, just docker-compose fails Steps to reproduce the behavior DD0033: does the host have Internet access? DD0030: is the image access management authorized? DD0032: do Docker networks overlap with host IPs? DD0010: is the Docker API proxy responding? DD0014: are the backend processes running? DD0015: are the binary symlinks installed? DD0017: can a VM be started? vm has not started: vm has not started DD0018: does the host support virtualization? DD0016: is the LinuxKit VM running? vm is not running: vm has not started DD0011: are the LinuxKit services running? DD0028: is there available VM disk space? DD0027: is there available disk space on the host?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |