They won't apply unexpectedly, so you can reboot at a time that suits. Unless there's a specific security risk there's no need to apply them frequently. Total downtime is the length of a restart, which is also nice and easy.
It won't fit every use-case, but if you're looking for a zero-maintenance containerized-workload option, it can't be beat.
It's the kind of thing I host so that no matter what device I'm sitting in front of, I can easily pull it up. Hence a server is needed. I'm not talking about just my own laptop or phone, I mean any shared or borrowed device.
I find it so useful I pull it up almost every workday.
What do you mean by that? Podman compose is a drop-in replacement for Docker compose, and everything is identical other than needing to add :Z to the end of your volume lines.
Here's my Navidrome config. This is running on uCore version of CoreOS, with rootless Podman and SELinux. I made no configuration changes to Podman out-of-the-box, and this is the full compose file.
i have to remap the user namespace
Note: I have not done this. What are you running Podman on? Perhaps there is some config issue with the host, since you're having issues with many containers?
To be fair, maybe just go with docker if it's causing that much pain. But again, mine is working OOTB without making any changes to the Podman setup on ucore, and using the config below.
I'm not the OP, so I wasn't having a conversation with them. But to me it gives off the vibe of "Random stranger, you should do all the work for me and provide all the answers, because I'm too lazy to do any of it myself."
In case it's useful, I switch to self-hosting once I found out that you can use Gluetun to force ALL torrenting traffic down a VPN tunnel. Now I run everything myself for the price of a VPN, and never have to worry about a letter from my ISP.
That statistic isn't particularly useful. They complied with requests, but their response might have been "We don't know anything."
The only thing they can provide in regards to email is an IP address, which can be circumvented by using the VPN, which doesn't log IP addresses. You obviously shouldn't have a recovery email on your account, so they can't provide that.
In my case, I couldn't care less if they provided my IP address. I'm not doing anything illegal, I just prefer my email to be stored encrypted so server admins can't read it.
They won't apply unexpectedly, so you can reboot at a time that suits. Unless there's a specific security risk there's no need to apply them frequently. Total downtime is the length of a restart, which is also nice and easy.
It won't fit every use-case, but if you're looking for a zero-maintenance containerized-workload option, it can't be beat.