←back to thread

I ditched Docker for Podman

(codesmash.dev)
1101 points codesmash | 2 comments | 05 Sep 25 11:56 UTC | HN request time: 0.419s | source
Show context
CraigJPerry ◴[05 Sep 25 14:15 UTC] No.45138862[source]▶
Docker is failing in that trap where they feel the need to try (and mostly fail so far) to add net-new value streams (e.g. mcp catalogue, a bunch of other stuff i immediately turned off that last time i installed it) rather than focus on the core value.

It's not the case that they've maximised the utility of the core build / publish container nor the acquire / run container workflows and but they're prioritising fluff around the edges of the core problem.

Podman for its various issues is a whole lot more focussed.

replies(2): >>45138998 #>>45146299 #
jen20 ◴[06 Sep 25 03:10 UTC] No.45146299[source]▶
They have the second problem that `container` [1] will eat up a ton of their business when it ships properly in a month or two.

[1]: https://github.com/apple/container

replies(1): >>45151380 #
1. mdaniel ◴[06 Sep 25 17:48 UTC] No.45151380[source]▶
uh-huh, maybe for the corps that have a predictable hardware refresh schedule but I've never worked in such a place https://github.com/apple/container#:~:text=is%20supported%20...
replies(1): >>45152329 #
2. jen20 ◴[06 Sep 25 19:49 UTC] No.45152329[source]▶
Why does the hardware refresh schedule matter? What you appear to be referring to is the _operating system_ refresh schedule, which should be every year even at enterprises where corporate IT is problematic.