👍

That’s really interesting. What about 0.0.0.0? Does it resolve to localhost or the “public” ip?

You didn’t like flying through 150 rings?

From wikipedia

It was invented by Alexander Cumming in 1775 but became known as the U-bend following the introduction of the U-shaped trap by Thomas Crapper in 1880

Are you shitting me?

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

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

I’m just gonna leave this here

https://piped.video/watch?v=b93IBwJ_Yow

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

Was thinking “Oh shit now I have to become vegan”, but the article is paywalled so I didn’t have to go on the guilt trip.

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.