8

Docker.
Tried very hard to like it.
Went through every possible option of making it work properly in every situation.
Ever since the licensing bullshit it has really gone to shit.

Comments
  • 2
    Try podman.
  • 0
    @spongessuck I've used Podman and it works, but it's API isn't complete. Last time I tried, it couldn't even handle gzipped images. If you want to do anything advanced or use bindings, you often need to find Podman specific libraries instead of Docker ones.

    I used it for months on my home server but went back to docker due to docker-compose compatibility issues
  • 1
    Licensing? I must be out of the loop. Never tried podman, but hey if it works and makes things easier, that's awesome. Docker is an amazing tool, just has a bit of a learning curve.
  • 0
    I have a love hate relationship with Docker. I understand a lot about advanced Linux packing. At its core, Docker is just chroot + cgroup + a layered filesystem. It's really kinda amazing how it works.

    But the repository of images sucks ass. There's no way to properly version or have metadata for update paths. Of all the things Moby/Docker could be charging for, they can't even fix the core issues that's causing unconstrained growth of images. I've written about Docker Orchestration systems here:

    https://battlepenguin.com/tech/...

    I started this project as an attempt to solve the issue of versioning upgrades, by basing all my containers on Nix:

    https://gitlab.com/djsumdog/nixbee/

    but it's got a long way to go.
  • 0
    @nosoup4u DockerDesktop has had an enterprise licensing charge for years. But you can just install the command line tool/daemon (on Windows/Mac) and avoid it.
Add Comment