Comment by jasonlotito | Hacker News Reader

Comment by jasonlotito | Hacker News Reader

Parent Full thread

"OrbStack is a drop-in replacement for Docker Desktop"

First thing I try is searching for container images to pull down to use in OrbStack to try it out... and nope, can't do that from what I can see.

"Switching from Docker Desktop is painless: just open OrbStack and get started."

So, no, not a drop-in replacement for Docker Desktop.

Then I look at CPU usage after closing down OrbStack, and it's still running at 265% CPU usage doing nothing.

Memory in Docker Desktop is customizable, with a default 8GB. No mention of them adjusting that in the benchmark.

I don't know... bunch of fishy stuff here that doesn't sit well with me. The "drop in replacement" part didn't sit well with me, but then seeing 265% CPU usage... let's just say it's not a good start in my book.

It is a public beta, so sure, things can improve.

I just tried it with my JetBrains Rider setup where we develop against containers. Turned off Docker Desktop, started up Orbstack. All worked the same. Debugging/etc. Started up the docker containers without issue and don't see any CPU issues. I'm on a Mac M1 pro. I'll keep trying it and see if it continues to work well in the long term.

Hey, dev here. 265% CPU usage doing nothing is definitely not normal and could be a bug of some sort. Can you share what you were doing before closing it, and even better, send log files (OrbStack menu -> Show Logs) to logs@orbstack.dev or open an issue on GitHub [1]? Happy to look into this and fix it.

Not sure what you mean about the images: you can pull images with the Docker CLI, and we'll add a GUI for managing images soon. To migrate images from Docker Desktop: https://github.com/orbstack/orbstack/issues/90

There's not enough space to put "Initial memory" in the landing page tab but the docs do clarify that the measurement is for initial memory usage: https://docs.orbstack.dev/benchmarks#initial-memory-usage

Re memory usage: One of our advantages over Docker Desktop is that memory is allocated on demand, so I think it's fair. (Unfortunately this doesn't include releasing memory dynamically due to a macOS bug combined with security restrictions: https://docs.orbstack.dev/efficiency#dynamic-memory)

Either way, thanks a lot for sharing your thoughts!

[1] https://orbstack.dev/issues/bug

Reply on news.ycombinator.com