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.