In case you omitted the following out of ignorance and not by deliberate choice:

podman unshare can be used to (mostly) painlessly access the files created by rootless podman.

Thankfully the birds are often content to do most of the talking

For those curious about how this fork came to be, KnowYourMeme had a decent rundown: https://knowyourmeme.com/memes/events/godot-engine-user-blocking-controversy-wokot

I guess it only makes sense that after Liquid Ass UI, we’d get Fuzzy Toilet Seat UI

I hesitate to bring this up because you’ve clearly already done most of the hard work, but I’m planning on attending the following conference talk this weekend that might be of interest to you: https://fosdem.org/2026/schedule/event/VEQTLH-infrastructure-as-python/

ehehehehe thanks for that mental image

Of course, one can always reclaim that space if the data truly is inaccessible. Makes me want to write a joke program for “cleaning up” after ransomware that just removes the data from the partition table (or whatever the equivalent for files is - would that just be rm?)

shred -f -u

I recently went from 0 to 1. Reinstalled my VPS under debian, and decided to run my forgejo instance with their rootless container. Mostly as a learning experience, but also to easily decouple the forgejo version from whichever version my distro packages.