91–100 of 152 posts
Protip: if you want to use Podman (or Podman Desktop) with Docker Compose compatibility, you'll have a better time installing podman-compose [1] and setting up your env like so: alias docker=podman # If you want to still use Docker Compose # export PODMAN_COMPOSE_PROVIDER=docker-compose # On macOS: `brew install podman-compose` export PODMAN_COMPOSE_PROVIDER=podman-compose export PODMAN_COMPOSE_WARNING_LOGS=false Mos…
Earlier quoted context omitted.
What’s the point of using a distribution if you need to find back ports or build your own? Distros are, after all, mostly collections of installable software.
The point is that it works 95% of the time, or probably more like 98%. If this is a e.g. webserver and I only need my fastcgi backend built by myself, I can still have reverse proxy, database, and every other package be done by the distro. No one said you need backports. More like: If it fits 90% and one package doesn't work, you get it from somewhere else - that doesn't invalidate the concept of a distro for me. YMM…
Reverse proxy, DB, etc from Debian. The application server is built and deployed with nix. The Python version (and all the dependencies) that runs the application server is the tagged one in my nix flake which is the same used in the development environment.
I make sure that PostgreSQL is never upgraded past what is available in the latest Debian stable on any on the dev machines.
And while we’re at it, what’s your favorite non-sudo Docker alternative? And why?
Just want to say everyone should be using podman. Its architecture is way more sane and integrates with Linux on a far more basic level (a regular process that can be started via systemd, etc. instead of a root daemon. Run it as root to get privileged containers). They've also built an incredible ecosystem around podman itself. Red Hat has been absolutely cooking with containers recently.
What are the benefits of using Podman and not Docker?
Protip: if you want to use Podman (or Podman Desktop) with Docker Compose compatibility, you'll have a better time installing podman-compose [1] and setting up your env like so: alias docker=podman # If you want to still use Docker Compose # export PODMAN_COMPOSE_PROVIDER=docker-compose # On macOS: `brew install podman-compose` export PODMAN_COMPOSE_PROVIDER=podman-compose export PODMAN_COMPOSE_WARNING_LOGS=false Mos…
podman compose is really bad
Podman is interesting as well because it can run Kubernetes yamls (to a small extent) which can be handy.
Earlier quoted context omitted.
No root daemon got replaced with "but if you want a replacement for docker compose you ought to be using systemd (quadlets)". Meh
Incorrect, the use of a non-root daemon is essential for isolation and security.