Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: Container Desktop – Podman Desktop Companion

container-desktop.com

Post reply on HN
Print view View original

71–80 of 207 posts

Re: Show HN: Container Desktop – Podman Desktop Companion

#72

Post by cweagans »

throwanem wrote: post #10
cweagans wrote: post #9

Earlier quoted context omitted.

Another enthusiastic +1 for OrbStack. It's fantastic.

GPU support would be a real benefit, but for anything not needing that, Orbstack's become my strong preference.

Is there anything you can actually _do_ with the Apple GPUs outside of macOS? I know the Asahi Linux person was working on a driver for it, but is it in a useful state?

Re: Show HN: Container Desktop – Podman Desktop Companion

#73

Post by istoica »

swyx wrote: post #25
hnlmorg wrote: post #7

If you’re on macOS, then Orbstack is a nice alternative to Docker Desktop (I’m not affiliated with Orbstack)

colima is also good https://www.swyx.io/running-docker-without-docker-desktop also no affiliation and have not tried orbstack

Colima offers the best experience for docker alternative. LIMA offers the equivalent of WSL, where both docker and podman are supported. I like LIMA a lot as I deal with both, but COLIMA rocks for simplicity. I think COLIMA + Container Desktop are perfect replacement on mac for traditional Docker Desktop users.

Re: Show HN: Container Desktop – Podman Desktop Companion

#74

Post by appendix-rock »

GiorgioG wrote: post #66
istoica wrote: post #45

Kubernetes is planned - my devops wants me to add it badly! Author note - Most of you guys here are power users, for whom UI is a visual poem that you need or not. This is not a commercial project, it is not following any business goals. But this does not mean concessions to quality, it does try to offer minimal resource usage everywhere, easy experience, good UI/UX. It explains all it does behind the scenes if you e…

[flagged]

Your basically-absolutist stance is about as unenlightened as the one that you’re arguing against.

Re: Show HN: Container Desktop – Podman Desktop Companion

#76

Post by GiorgioG »

abuani wrote: post #70
GiorgioG wrote: post #66

Earlier quoted context omitted.

[flagged]

Like everything in tech, it's all about tradeoffs and understanding how you want to scale your business. Of the three startups I've been at, 2 of them adopted k8s early on and 1 of which didn't. Of the two that adopted k8s, one I would say k8s was our key differentiator in terms of our GTM motion and how our platform powered the business. $MM customer needs a setup running as close to their current infra's region for…

You don’t need k8s to scale. Can you make other poor choices? Sure.

Re: Show HN: Container Desktop – Podman Desktop Companion

#77

Post by [deleted] »

GiorgioG wrote: post #66
istoica wrote: post #45

Kubernetes is planned - my devops wants me to add it badly! Author note - Most of you guys here are power users, for whom UI is a visual poem that you need or not. This is not a commercial project, it is not following any business goals. But this does not mean concessions to quality, it does try to offer minimal resource usage everywhere, easy experience, good UI/UX. It explains all it does behind the scenes if you e…

[flagged]

[deleted]

Re: Show HN: Container Desktop – Podman Desktop Companion

#78

Post by mook »

jve wrote: post #65
bityard wrote: post #63

Earlier quoted context omitted.

I don't know if your comment was intended to imply that Docker was against the Unix philosophy in some way (a debatable point, but not really one I share), or if you mean that the tools don't follow a lot of common Unix convension. When Docker was only a few years old, I did keep running into lots of small things which implied that the people developing docker in fact did NOT have a Unix (or even Linux) background. T…

Why is newline at the end relevant? I remember not having a newline breaks some tools... but why? It can't be because of unix philosophy!?

Some old tools had bugs where they'd read a line (up to the new line) and then process it, so if the last line didn't end with a new line they'd never do the processing. So a manual workaround for bugs became the convention.
Post reply on HN