Non ho mai avuto un rapporto idilliaco con le distribuzioni basate su RPM, eppure openSUSE ha del potenziale, specie nella sua variante MicroOS.

Non ho mai avuto un rapporto idilliaco con le distribuzioni basate su RPM, eppure openSUSE ha del potenziale, specie nella sua variante MicroOS.
My advice on SELinux container labeling | Red Hat Developer https://developers.redhat.com/articles/2025/04/11/my-advice-selinux-container-labeling?sc_cid=RHCTG0250000446542 #containers #podman #docker #selinux
Podman Desktop 1.18 is here! Enjoy enhanced Docker compatibility, easy Kubernetes namespace switching, job viewing, and improved status bar providers. Check out the details on the Podman Blog.
https://podman-desktop.io/blog/podman-desktop-release-1.18
#podmanDesktop #podman #container #Kubernetes
Podman Desktop v1.18 has just dropped! The Docker compatibility features are no longer experimental, improvements in Task bars, K8s namespace switching, K8s jobs, plus more! Details: https://podman-desktop.io/blog/podman-desktop-release-1.18 #podman #opensource
Now my Java based deployment worker generates one shell script per deployment in order to ease its understanding
Eigener Mailserver mit Stalwart
Der Artikel zeigt das Aufsetzen von Stalwart mittels (rootless) Podman Quadlets.
Join us this Thursday, April 24, from 9 to 10 AM EST for the #Podman-Desktop Community meeting! Engage with the developers, pose your inquiries and share your experiences! You can find the meeting details and agenda at this link : https://github.com/podman-desktop/community/issues/4
Jellyfin Dockerfile has this line:
HEALTHCHECK --interval=30s --timeout=30s --start-period=10s --retries=3 \
CMD curl --noproxy 'localhost' -Lk -fsS "${HEALTHCHECK_URL}" || exit 1
so I've added the following to my jellyfin.container:
...
HealthCmd=curl --noproxy 'localhost' -Lk -fsS http://localhost:8096/health || exit 1
HealthStartPeriod=10s
HealthInterval=30s
HealthTimeout=30s
HealthRetries=3
Notify=healthy
...
https://github.com/jellyfin/jellyfin-packaging/blob/master/docker/Dockerfile
Vaultwarden Dockerfile has this:
HEALTHCHECK --interval=60s --timeout=10s CMD ["/healthcheck.sh"]
so I've added the following to my vaultwarden.container:
...
HealthCmd=/healthcheck.sh
HealthStartPeriod=10s
HealthInterval=60s
HealthTimeout=10s
HealthRetries=5
Notify=healthy
...
https://github.com/dani-garcia/vaultwarden/blob/main/docker/Dockerfile.debian
For caddy, I used wget and a custom subdomain.
caddy.container:
...
HealthCmd=wget --no-verbose --tries=1 --spider https://test.example.com/health-check || exit 1
HealthStartPeriod=10s
HealthInterval=30s
HealthTimeout=5s
HealthRetries=5
Notify=healthy
...
Caddyfile:
...
test.example.com {
respond /health-check 200
respond "Hello, world!"
}
...
Inspiration:
1) https://caddyserver.com/docs/caddyfile/directives/respond
I'm on a podman healthcheck quest.
When the pi-hole Dockerfile has:
HEALTHCHECK CMD dig -p $(pihole-FTL --config dns.port) +short +norecurse +retry=0 @127.0.0.1 pi.hole || exit 1
you need something like:
...
HealthCmd=dig -p $(pihole-FTL --config dns.port) +short +norecurse +retry=0 @127.0.0.1 pi.hole || exit 1
HealthStartPeriod=10s
HealthInterval=30s
HealthTimeout=5s
HealthRetries=5
Notify=healthy
...
in the .container file.
Next up: caddy
https://github.com/pi-hole/docker-pi-hole/blob/master/src/Dockerfile
Meine Planungen für die Migrationsorgie Ostern gehen gerade den Bach runter.
Hhmpff!
Simplify AI data integration with RamaLama and RAG
https://developers.redhat.com/articles/2025/04/03/simplify-ai-data-integration-ramalama-and-rag#
#Docling #Ramalama #podman #aiml
Incredible how Alexander Larsson was ahead of times with that reply about sharing libraries, it's basically the approach by Docker images... but OSTree, used by Flatpak, predates Docker and it is even more efficient with its by-file deduplication. And the recent #ComposeFS by the same author will allow #Podman containers to have the same deduplication not only on disk but even on RAM (to my understanding)
Finally moved my home server off of docker and onto podman. The holdout was Taiga which was using docker compose. Despite already deploying a few simpler services with podman, I still didn't know before this how podman does hostnames, how to set up a network with a quadlet, and using PVCs.
My favourite troubleshooting trick of "Delete it and get it to recreate when you restart the thing" turned out to the be the correct choice after a day of furtleing about with #podman networking.
#til podman lepiej wspiera pliki kubernetes niż pliki docker compose. I super, bo właśnie korzystam z niego do testowania, a środowisko produkcyjne mam na k8s, czyli nie muszę mieć oddzielnego pliku dla compose
So Podman and IPv6 is challenging me. Having created a ipv6-enabled podman network and assigning that to a container. The container appears to be reachable on both the IPv4 and IPv6 interfaces. The thing I cannot figure out is the publishing of ports. I have not found a way to make both interfaces accessible from external. For IPv4 -p 80:80 does the trick, but not IPv6. What am I missing? #Podman