asciinema VS storage

> https://github.com/asciinema/asciinema-server

and

> Web player for terminal session recordings

It's not mine, it's asciinema, lol. I tried finding it, but fell short, look around here https://github.com/asciinema/asciinema-server/tree/develop/assets/css.

I've used the script command and asciinema [1] before. Easy way to record steps without missing anything.

[1] https://asciinema.org/

You're welcome! I just stumbled across another one that looks promising, too: https://asciinema.org/

Check out https://asciinema.org, a tool for recording terminal commands.

These days I reluctantly prefer embedding a static screenshot in my READMEs with a link to an asciinema animation. They're easy enough to record, and at least I'm not costing some poor sod who accidentally loaded my page $0.10 to download a giant GIF on mobile data.

I you'd like to know what it is like to use Podman, I've found those Asciinema snippets by Matthew Heon (Podman contributor) quite helpful: https://asciinema.org/~mheon

Check here: https://github.com/containers/storage/blob/main/docs/containers-storage.conf.5.md

One example that keeps popping up over the years is containers and ZFS or more specifically Linux kernel namespaces and ZFS. First LXD in 2016, podman in 2020 and 2021. There is docker issues in the past as well with the ZFS storage driver or overlayfs. These issues are fixed rather quickly by ZFS (because they are very good at what they do) or by upstream, but bugs keep happening. It is something I do not want to deal with. As I expect future problems with ZFS and projects that depend on specific features of the linux kernel, I prefer using something else. In this case Stratis, LVM and XFS, or LVM and ext4.

I tried using NFS because I know it well, and it is easy to do using ZFS. This Red Hat blog post says NFS should work and it does not work at the same time. I decided to just try. The ZFS server has no idea about the subuids on the podman host, so I had to mess around with --uidmap and --gidmap. That worked, as long as I did not use a pod. To keep things neat and simple, I tried to put all my Nextcloud containers into one pod. However, the id-mapping features cannot map multiple container IDs to the same host IDs. So, I cannot map the www-data (70) user and the postgres (82) user to localadmin (1000) on the podman host. Next, I tried directly mounting the NFS share as a volume using the '--opt type=nfs4' option when creating the volumes. Right away, I learned that rootless containers can't mount network shares. Makes a certain kind of sense and is also documented in the man page. But I first tried using root containers, to prove out the concept. The volumes mounted without complaint, but I landed back at square one because the id-mapping is not applied anywhere now. Appears to me that, NFS is a complete dud for this kind of application.

Docker is properly attributed to, see https://github.com/containers/storage/blob/a4cc7aa79e050c976...

I think OP wanted to say that Podman hates Docker what is not I feel when I'm interacting with the community there. People who use Podman do it because of it's additional features that Docker does not have, like starting an Container from a rootfs or mounting the currect directory in a container using "." as path. It's a lot of small things that make Podman better.