This is a goldmine of #podman #networking tricks:
Example: Use socket units with `ReusePort=true` for your container units to let multiple containers share one port and let the kernel do the load-balancing via SO_REUSEPORT
This is a goldmine of #podman #networking tricks:
Example: Use socket units with `ReusePort=true` for your container units to let multiple containers share one port and let the kernel do the load-balancing via SO_REUSEPORT
Hi @Greylinux and if you are interested in #Quadlets for #OpenCloud you might wanna support the feature request at URL: https://github.com/orgs/opencloud-eu/discussions/1498
This has been what's it's all been for...
Bots raising PRs when a container is updated. I have the ability to roll back these back if something goes wrong and the same is true of OS updates.
#TIL #podman #quadlets can also be defined through `.kube` files in the same way as can be usually done with `.container` units.
https://docs.podman.io/en/latest/markdown/podman-systemd.unit.5.html
I think I've come to the end of the road with bootc.
I've spent a good few months building up my #HomeLab with rootless #Podman and #Quadlets but getting a self hosted CI/CD pipeline to update the machine has been so painful, and now I've got everything "working" I'm finding issues like the one linked below.
I think I'm going to have to join the #NixOS band wagon and start over.
I know I can do podman or docker in Nix, but I'll want to do it fully Nix I think.
Explain what happens I've installed cockpit into Fedora-bootc On boot up I get the error below. It only started today, I'm not aware of anything I've done to cause a regression on my machine other ...
I find myself using quadlets more and more often, but the networking threw me for a loop when I first moved over from docker-compose.
Here's a quick post about getting your quadlets onto the same networks: