Live data from Hacker News

OrbStack 1.0 is here! Fast, light, easy way to run Docker containers and Linux

orbstack.dev

21–30 of 30 posts

Re: OrbStack 1.0 is here! Fast, light, easy way to run Docker containers and Linux

#21
post #3

Dev here, happy to answer questions!

Congrats on the launch!

I just updated and saw the notification and passed it along to my legal department to get approval for purchase.

Do you know if you are, or have any plans to be, SOC2 Compliant?

Re: OrbStack 1.0 is here! Fast, light, easy way to run Docker containers and Linux

#25
post #23
post #3

Dev here, happy to answer questions!

Can you share any long term plans past 1.0? Honestly it feels like a finished product already. Which is amazing for a 1.0!

Thanks! I won't be too specific because of a certain competitor looming on the horizon, but so far my plan is to focus on improving DX.

Re: OrbStack 1.0 is here! Fast, light, easy way to run Docker containers and Linux

#26
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.

Re: OrbStack 1.0 is here! Fast, light, easy way to run Docker containers and Linux

#27
post #3

Dev here, happy to answer questions!

Congrats on the launch! I just updated and saw the notification and passed it along to my legal department to get approval for purchase. Do you know if you are, or have any plans to be, SOC2 Compliant?

[deleted]

Re: OrbStack 1.0 is here! Fast, light, easy way to run Docker containers and Linux

#28

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.

orbstack 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

# Switch to OrbStack

docker context use orbstack

# Switch to Colima

docker context use colima

Re: OrbStack 1.0 is here! Fast, light, easy way to run Docker containers and Linux

#29
post #25
post #23

Earlier quoted context omitted.

Can you share any long term plans past 1.0? Honestly it feels like a finished product already. Which is amazing for a 1.0!

Thanks! I won't be too specific because of a certain competitor looming on the horizon, but so far my plan is to focus on improving DX.

Gotcha, totally understand. But I will say that ideas matter far less than the ability to deliver quickly and with high quality. IRC technically has nearly all of the same features as Slack and yet...

So far you're far ahead of the competition in multiple of the ways that matter most. I've tried all of the competition and I don't want any of it on my computer.

The fact that it is dead simple to install, migrate, and use also gives you a huge leg up when we consider adopting it for our company. I absolutely don't want to spin up a support channel to help people migrate to or troubleshoot podman or rancher.

Re: OrbStack 1.0 is here! Fast, light, easy way to run Docker containers and Linux

#30

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.

As 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

I suppose Orbstack should make it more obvious what it did and how to revert though.

Post reply on HN