3 ms·
I recently installed docker, podman, Colima, and Orbstack. Orbstack was the only one that overwrote the docker socket instead of connecting to the docker socket
by LargeTomato 3y ago
I recently installed docker, podman, Colima, and Orbstack. Orbstack was the only one that overwrote the docker socket instead of connecting to the docker socket. The containerization on my Mac is locked into using Orbstack because no other container engine can bind to that, now overridden, socket.
- myPhilTaylor 3y agoorbstack provides a docker engine and sets the socket to point at that. It's a complete system, it's not "just a gui for an existing docker instance". Your issue is your flawed understanding of what Orbstack is and not understanding docker contexts. You can use Docker contexts to run OrbStack and Colima side-by-side. Switching contexts affects all commands you run from that point on, see: https://docs.orbstack.dev/install#colima https://docs.orbstack.dev/install#colima # Switch to OrbStack docker context use orbstack # Switch to Colima docker context use colima
- mdeeks 3y agoAs the other commenter mentions, you can actually use `docker context` to choose which system you want to use for all of your tools. That docker socket you're referencing is just for the default context if you never chose anything. Personally, this is the behavior I want and I think that is correct. I just installed OrbStack. That means I want it to take over as the new way to use docker. Switching back to any other system is easy and it is documented here: https://docs.orbstack.dev/faq#revert-docker https://docs.orbstack.dev/faq#revert-docker I suppose Orbstack should make it more obvious what it did and how to revert though.