• 0 Posts
  • 71 Comments
Joined 2 years ago
cake
Cake day: June 12th, 2023

help-circle









  • 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
    






  • asap@lemmy.worldtoSelfhosted@lemmy.worldService monitoring
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    6 months ago

    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.)