As someone posted above, someone obtaining access to your encrypted data might lead to an issue in the future:

https://en.wikipedia.org/wiki/Harvest_now,_decrypt_later

smartphone app

It’s a PWA, just install the site on your phone as a native app. I’ve been using it for about a year.

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.

services:
  navidrome:
    image: deluan/navidrome:latest
    container_name: navidrome
    ports:
      - "3015:4533"
    restart: unless-stopped
    environment:
      # Optional: put your config options customization here. Examples:
    volumes:
      - ./data:/data:Z
      - ./config.toml:/navidrome.toml:Z

You need to add :Z to the end of your volume lines, or lowercase z for shared volumes.

I’m running 50+ containers, probably most of the popular ones, and all working fine.

I run 50+ containers with rootless Podman compose (on CoreOS) and haven’t encountered any unsolvable issues so far.

I’ve never tried quadlets but haven’t found a need or any driving reason to do so.

Move your stuff from Gandi to Netim.com

Gandi got acquired and has done some very weird shit with pricing.

It’s for a streaming service.

3 lines of text (which you can copy/paste from an existing entry) beats clicking around a web interface to set things up.

Plus you can do many more advanced things with Caddy which you can’t do in NPM. Caddy is just easier to use.

You can use Immich Public Proxy to share the albums without having to expose your Immich instance. You can use all the normal Immich options - password protected albums, and links that expire, etc

It’s just what I use, as I’m specifically looking for something which only notifies when things aren’t able to report due to failure. Free for 20 checks which is more than enough for me.

If I were hosting it myself I wouldn’t know if my own notification system had failed (since it wouldn’t be able to report due to failure.)

For Podman you don’t need anything else other than Podman to monitor and restart failed containers:

podman-compose --podman-run-args='--health-on-failure=restart' up -d

For anything else I use https://healthchecks.io/

They may have nothing to hide but they have IP to protect to stay in business. What a ridiculous thing to say.

It’s like YNAB4. For those of us in that vintage it’s perfect. If you’re using the newer YNAB it might have missing features.

The “minimal” part is incorrect; it is a super complicated container. The number of moving parts don’t leave me with any confidence that I could keep it running or fix any issues going forwards.

Mainly for security. I was originally looking at CoreOS but I liked the additional improvements by the UBlue team. Since I only want it to run containers, it is a huge security benefit to be immutable and designed specifically for that workflow.

The Ignition file is super easy to do, even for just one server (substitute docker for podman depending which you have):

Take a copy of the UCore butane file:

https://github.com/ublue-os/ucore/blob/main/examples/ucore-autorebase.butane

Update it with your SSH public key and a password hash by using this command:

# Get a password hash
podman run -ti --rm quay.io/coreos/mkpasswd --method=yescrypt

Then host the butane file in a temporary local webserver:

# Convert Butane file to Ignition file
podman run -i --rm quay.io/coreos/butane:release --pretty --strict < ucore-autorebase.butane > ignition.ign

# Serve the Igition file using a temp webserver
podman run -p 5080:80 -v "$PWD":/var/www/html php:7.2-apache

During UCore setup, type in the address of the hosted file, e.g. http://your_ip_addr:5080/ignition.ign

That’s it - UCore configures everything else during setup.___

Rootless Podman :) It requires you to learn a little bit of new syntax, for example, the way you mount volumes and pass environment variables can be slightly different, but there’s nothing that hasn’t worked for me.

I’m using this on uBlue uCore, which I would also strongly recommend for security reasons.

I switched and was very glad to do so. You increase your security and so far I haven’t seen any downside. Every container I’ve tried has worked without issues, even complex ones.

Just remember that Cloudflare decrypts and re-encrypts all your data, so they can read absolutely everything that passes through those tunnels.