Not sure how to do this

I’ve been trying, but haven’t found anything. When I first turned off secure boot, it worked great, but stopped working again once I updated

Going great! Loaded up Fedora on my HP laptop which has given it a new lease on life. Only downside is that it won’t just boot straight into the OS, otherwise GRUB freezes (not dual booting, secure boot is off), so I have to spam F9 on startup and select linux to boot into, then it works fine.

Started self-hosting some things on an old desktop I had lying around, and am planning on moving from iPhone to Graphene with my next phone

I’m interested where this comes from too. Is it just because they aren’t a FOSS project?

I went through all this, and it seems Jellyfin was the problem. I added this into my yaml:

ports: - "8096"

And now I can access the server…if I use port 32769…which I figured out by using docker compose ps -a. I also had restarted it once, and before the restart, I accessed it with 32768. Any idea on how to fix this? I don’t even know what’s causing it

UPDATE: For those keeping score at home, I needed to change the mount from /etc/caddy to /usr/share/caddy and now it works. However, I have a new problem:

Once I get all three containers (caddy, jellyfin, and tailscale) up and running, now I can’t access it. All three report as being up and I checked the logs and none list any errors, but when I go to my tailnet address, it can’t find anything. I’ve even put the port number in and it can’t find anything. Any ideas?

Thanks for the info, I’ll try using a different mount point. Which directory would be best?

Do not use /root inside or outside of a container for plain file access. That’s insane.

Yeah I agree, I don’t know where that came from in the initial error. That line in the yaml file had the path as ~/Jellyfin/jellyfin-tailscale/caddy/conf/Caddyfile so it was in my user directory

You also don’t mention if Podman is the underlying runtime managing the container

I’m not using Podman