Hacker News new | ask | show | jobs
by gigel82 203 days ago
People stuck with Docker for a reason, even after they became user hostile. Almost every selfhosted project in existence provides a docker-compose.yml that's easy to expand and configure to immediately get started. None provide generic OCI containers to run in generic OCI runtimes.

I understand sticking with compatibility at that layer from an "ideal goal" POV, but that is unlikely to see a lot of adoption precisely because applications don't target generic OCI runtimes.
1 comments
tlamponi 203 days ago
The one (docker compose) builds on top of the other (OCI images & runtimes).

We would have required to implement runtime integration anyway, and I hardly see any benefit in not releasing that lower level integration earlier.

link