Herr Irrtum! 🔊 🏳️🌈 on Nostr: #Debian13 / #Podman5 / #Pasta / #Gancio Whoa - I've debugged two long nights and had ...
#Debian13 / #Podman5 / #Pasta / #Gancio
Whoa - I've debugged two long nights and had one more nights with bad dreams about changing config files - before it finally occurred to me. Podman 5, the version coming with the upgrade from Debian12 to Debian13 (Podman v.4 before), has some SERiOUS breaking changes, I wasn't aware and I didn't felt "informed" enough — therefore this post:
If your Podman container running under Podman 5 has an automatic URL rule, where it changes all internal links to external links: To Links your hosts reserve proxy is presenting from the hosts main network interface - those links wont work.
And this is by far not uncommon. I'm running a quite huge Gancio instance, I am affected. So why is this? Podman v5 did change the base of its networking to something called "pasta". There are surly good reasons for this, but one of the main (anti) features of Pasta is: Connections from within containers to the main hosts IP won't work. At all.
This is btw. breaking the "marketing" claim of the Podman guys that Podman may be used as "in place" replacement of #Docker. No, this way this isn't working (and it wont work for other reasons as well, [hello to Nextcloud]).
So, whats a very effective and quick fix for this? Getting rid of Pasta!
So at least in Debian, cp /usr/share/containers/containers.conf to /etc/containers and make sure the network section contains this:
[network]
default_rootless_network_cmd = "slirp4netns"
(with the slirp4nets packages being installed).
Boom, it all works again.
See:
https://blog.podman.io/2024/03/podman-5-0-breaking-changes-in-detail/Published at
2026-03-02 20:00:14 CETEvent JSON
{
"id": "42d6dd3630b2b1ca1763b6ddb1c6b0d84e0571c32cda181105bb742c4b090f55",
"pubkey": "470925749c35844082b551ee5a4c3379a23d85209dfa591c614709efa8e4ecc9",
"created_at": 1772478014,
"kind": 1,
"tags": [
[
"t",
"debian13"
],
[
"t",
"podman5"
],
[
"t",
"pasta"
],
[
"t",
"gancio"
],
[
"t",
"docker"
],
[
"proxy",
"https://s.basspistol.org/notes/ajd3yikdq6",
"activitypub"
],
[
"client",
"Mostr",
"31990:6be38f8c63df7dbf84db7ec4a6e6fbbd8d19dca3b980efad18585c46f04b26f9:mostr",
"wss://relay.ditto.pub"
]
],
"content": "#Debian13 / #Podman5 / #Pasta / #Gancio \n\nWhoa - I've debugged two long nights and had one more nights with bad dreams about changing config files - before it finally occurred to me. Podman 5, the version coming with the upgrade from Debian12 to Debian13 (Podman v.4 before), has some SERiOUS breaking changes, I wasn't aware and I didn't felt \"informed\" enough — therefore this post:\n\nIf your Podman container running under Podman 5 has an automatic URL rule, where it changes all internal links to external links: To Links your hosts reserve proxy is presenting from the hosts main network interface - those links wont work. \n\nAnd this is by far not uncommon. I'm running a quite huge Gancio instance, I am affected. So why is this? Podman v5 did change the base of its networking to something called \"pasta\". There are surly good reasons for this, but one of the main (anti) features of Pasta is: Connections from within containers to the main hosts IP won't work. At all.\n\nThis is btw. breaking the \"marketing\" claim of the Podman guys that Podman may be used as \"in place\" replacement of #Docker. No, this way this isn't working (and it wont work for other reasons as well, [hello to Nextcloud]).\n\nSo, whats a very effective and quick fix for this? Getting rid of Pasta!\nSo at least in Debian, cp /usr/share/containers/containers.conf to /etc/containers and make sure the network section contains this:\n\n\n[network]\ndefault_rootless_network_cmd = \"slirp4netns\"\n(with the slirp4nets packages being installed).\nBoom, it all works again.\n\n\nSee:\n\nhttps://blog.podman.io/2024/03/podman-5-0-breaking-changes-in-detail/",
"sig": "894558ce165054990fc6fecf70f253ecb3fcb3cf025e91f639bd9fa5acb7fb8d287befa13c7138932ca0cc8547a2a60499cf10bdf2618f8ac4e892f52a7fc5f4"
}
