For me, setting up colored man pages is essential. I was hoping to see that in this article, because my methods aren’t ideal.

I’m either holding most back a couple versions, using a personal version of gentoos man pager that relies on texinfo and breaks on fedora, or using vim which is not my favorite.

I found this. I didn’t look at the code at all but the Readme mentions another project that might help.

https://github.com/ipatix/libvirt-usb-hotplug

You didn’t like flying through 150 rings?

it still mounts and at first glance seems to be working

What makes you say that?

Show us the output of things like lsblk, mount and cat /etc/fstab to give us a fuller picture

I use privatebin. Has some good features but I dont think it has login

I like to put mine in /var/local/movies etc. to keep the root standard and uncluttered.

Of course it’s just personal preference

Where’s the source code? Seriously, the only thing I can find for drive & calander are repos that were archived in 2021

I think that it’s definitely a good case for overlaying with install. They say to use it sparingly because it increases the chances of something breaking, but that doesn’t mean it will. Something like a VPN usually needs liw level access that container isolation makes difficult.

I’ve only had 1 issue on silverblue years ago where I couldn’t update because I had vim overlayed and they fixed it within a day or two.

You can set up multiple remotes for a repo and push to a local git server and github at the same time

Try running docker logs for the tailscale container to see if it gives any more info

Bash is my login shell, but I have fish set as the default shell for alacritty

Tailscale keeps the private keys locally, . It just facillitates setting up wireguard. They could steal your private keys, as could any program you install with root access. But it would comepletely destroy their business, and it’s open source. I really dont think they have anything to gain by tricking everyone

Have you tried taking the metwork config out of the compose file and just letting podman handle it?

Gender really is a complex topic huh?

I am root I am admin I am user I am all.

Holy shit I almost died

Just to offer the other perspective. I started with podman years ago. I knew very little about containers and I would say it made the learbing curve a lot steeper. Most guides and README’s use docker and when things didnt work I had to figure out if it was networking, selinux, rootless, not having the docker daemon, etc… without understanding fully what those things were because I didn’t know docker. But when I started running stuff on kubernetes, it was really easy. Pods in podman are isomorphic to kubernetes pods. I think the pain was worth it, but it was definitely not easy at the time. Documentation, guides, and networking have improved since then, so it may not be as big of a deal now

Quadlets with podman have completely replaced compose files for me. I use the kuberentes configs. Then I run a tailscale container in the pod and BAM, all of my computers can access that service without have to expose any ports.

Then I have an ansible playbook to log in to the host and start a detached tmux session so my user systemd services keep running. Its all rootless, and just so dang easy.