lingo.lol is one of the many independent Mastodon servers you can use to participate in the fediverse.
A place for linguists, philologists, and other lovers of languages.

Server stats:

66
active users

#podman

1 post1 participant0 posts today
Continued thread

12 Tage war #FreshRSS krank. Nun läuft es wieder, Gott sei Dank.

✅ #Restore mit #restic
✅ Havarierte InnoDB repariert und Datenbestand gerettet
✅ Containerlandschaft mit #nginx ProxyManager und aktueller #MariaDB via #Podman lokal
✅ Deployment auf 24x7 Server mit #RAID6

Nun fehlt noch das Upgrade von 1.19 auf die aktuelle Release. Habe das lange sträflich schludern lassen, aber in der aktuellen Containerlandschaft ist es auch leichter, alles sauber zu halten.

Jetzt hab' ich einen #RaspberryPi 1 über...

#Apple tries to contain itself with lightweight #Linux #VM for #macOS
Swift-based containerization framework aims to improve performance and security
Based on #OCI images, users can run them in a wide variety of server environments and data centers using orchestration tools like #Kubernetes.
Mac devs already have options for creating #containers, including #Docker, #Podman, Orbstack & Lima. But Docker and Podman, at least in the past, have not performed particularly well.
theregister.com/2025/06/10/app

The Register · Apple tries to contain itself with lightweight Linux VMs for macOSBy Thomas Claburn

I am migrating my whole container environment on macOS and Linux from Docker to Podman - right now I didn’t experience any issues on Linux. Do you think it will run as smoothly on macOS as well? Are there any caveats? I think Podman is a 100% replacement with more advantages than disadvantages (are there any?) Please share your opinions. #docker vs. #podman #changemymind

Saturday morning tradition: Reboot the #HomeLab.

VMs patch overnight. When I get up, I run a script to patch the host (#Debian), and reboot. On boot, after the script confirms internet access, all my #Podman #Container images are deleted and refreshed.

Since I started doing this I've improved my scripting abilities, thing are more stable and I rest a little easier knowing that if something goes wrong when I'm away my family won't be stuck without automations and services they are used to.

Huh, I've just noticed a strange property of #Docker / #Podman containers. If you start one in the simplest interactive way, e.g.

docker run --rm -it debian:stable

then the shell you get is bash – but SHELL isn't set in the environment, so if you run a subprocess that wants to spawn a subshell (like 'script'), the subshell is unexpectedly dash.

Confused me even more because 'echo $SHELL' in bash _does_ print "/bin/bash" – but it turns out that SHELL hasn't been exported to the environment, so it's just an internal shell variable!

I've gone through the exercise of spinning up multiple #podman rootless containers, and I've had to use `--userns` for several containers in which a host directory is mounted as a volume.

Say I've created a `postgres` user that runs the rootless postgres container, and its id is `1004`. The postgres container user id is `1001`. Unless the ids are mapped using `--userns=keep-id:uid=1001,gid=1001`, the container will exit when trying to write to the mounted directory.

docs.podman.io/en/latest/markd

docs.podman.iopodman-run — Podman documentation

Estoy experimentando con el CMS #Ghost. Si queréis instalar el contenedor #Docker sobre #Podman en #Fedora, este es el comando que mejor me ha ido hasta ahora:

podman run -d --name nombre-contenedor --userns=keep-id -e NODE_ENV=development -e url=http://localhost:3001 -p 3001:2368 -v /ruta/dentro/de/tu/directorio/personal:/var/lib/ghost/content:Z docker.io/ghost

And another system and container update has broken nextcloud-aio on podman completely.

Container's start script can't resolve DNS, even when explicitly given a --dns=1.1.1.1

No issues with othe containers. Nextcloud-aio tries to configure a lot networking stuff itself...

This is the part of self-hosting that sucks.