• Login
  • Register
  • Login Register
    Login
    Username/Email:
    Password:
    Or login with a social network below
  • Forum
  • Website
  • GitHub
  • Status
  • Translation
  • Features
  • Team
  • Rules
  • Help
  • Feeds
User Links
  • Login
  • Register
  • Login Register
    Login
    Username/Email:
    Password:
    Or login with a social network below

    Useful Links Forum Website GitHub Status Translation Features Team Rules Help Feeds
    Jellyfin Forum Support Troubleshooting Server discoverability - jellyfin with podman quadlet

     
    • 0 Vote(s) - 0 Average

    Server discoverability - jellyfin with podman quadlet

    Can't discover my jellyfin server on my network when running jellyfin with quadlet (podman + systemd)
    shoebill
    Offline

    Junior Member

    Posts: 1
    Threads: 1
    Joined: 2025 May
    Reputation: 0
    #1
    2025-05-19, 06:35 PM
    Hi,

    I'm trying to run a jellyfin server as a podman quadlet on my PC. The server is up and running, and I can play stuff in the web client on my PC. However, I can't discover this service on my network so I can play it on my android TV.

    Here's my configuration file:

    Code:
    [Unit]
    Description=jellyfin

    [Container]
    Image=docker.io/jellyfin/jellyfin:latest
    AutoUpdate=registrymedia
    PublishPort=8096:8096/tcp
    UserNS=keep-id
    Volume=jellyfin-config:/config:Z
    Volume=jellyfin-cache:/cache:Z
    Volume=/var/mnt/docs/media:/media:Z
    PublishPort=7359:7359/udp
    PublishPort=1900:1900/udp

    [Service]
    # Inform systemd of additional exit status
    SuccessExitStatus=0 143

    [Install]
    # Start by default on boot
    WantedBy=default.target

    I've tried a few things here based on googling.

    Code:
    PublishPort=7359:7359/udp
    PublishPort=1900:1900/udp

    I also tried this:

    Code:
    Network=host

    But got the following error on startup:

    Code:
    May 19 21:48:31 bazzite jellyfin[103277]: Port mappings have been discarded as one of the Host, Container, Pod, and None network modes are in use
    May 19 21:48:31 bazzite podman[103277]: 2025-05-19 21:48:31.895129718 +0400 +04 m=+0.031102629 container create 01c33362d2e32c02822463dec1d90e0a8cbce8e0176776539773daf41f7dd01f (image=docker.io/jellyfin/jellyfin:latest, name=systemd-jellyfin, org.opencontainers.image.url=https://je>
    May 19 21:48:31 bazzite conmon[103300]: conmon 01c33362d2e32c028224 <nwarn>: runtime stderr: mount `sysfs` to `sys`: Operation not permitted
    May 19 21:48:31 bazzite conmon[103300]: conmon 01c33362d2e32c028224 <error>: Failed to create container: exit status 1
    May 19 21:48:31 bazzite podman[103277]: 2025-05-19 21:48:31.877878081 +0400 +04 m=+0.013850992 image pull bb8553ab0efe4b205734408fbd790684dfba22985f1fdef43453ba055fbb2339 docker.io/jellyfin/jellyfin:latest
    May 19 21:48:31 bazzite podman[103277]: 2025-05-19 21:48:31.990545595 +0400 +04 m=+0.126518506 container remove 01c33362d2e32c02822463dec1d90e0a8cbce8e0176776539773daf41f7dd01f (image=docker.io/jellyfin/jellyfin:latest, name=systemd-jellyfin, org.opencontainers.image.url=https://je>
    [b]May 19 21:48:31 bazzite jellyfin[103277]: Error: crun: mount `sysfs` to `sys`: Operation not permitted: OCI permission denied[/b]
    May 19 21:48:31 bazzite systemd[1]: jellyfin.service: Main process exited, code=exited, status=126/n/a
    bitmap
    Offline

    Community Moderator

    Posts: 794
    Threads: 9
    Joined: 2023 Jul
    Reputation: 26
    #2
    2025-05-19, 07:29 PM
    Forgive me, I'm not super familiar with podman as I use docker compose. I see a few things here that I might be able to put you on the right track...

    1. You can't map ports with something like host network mode with compose because that mode exposes the container to the host's network. That's the first error I believe.

    2. That second error looks like you're trying to mount something that's not possible for one reason or another. Doesn't appear to be network related.

    3. I was about to paste a compose file when I found this: https://jellyfin.org/docs/general/post-i...t-bindings

    That explains what the ports are. So you would want 7359 published I believe, since that's client discovery. I'd look at fixing that second error and see what happens. You may also want to see if you can use the IP:PORT address for the server with your client and find/access it.
    Jellyfin 10.10.7 LSIO Docker | Ubuntu 24.04 LTS | i7-13700K | Arc A380 6 GB | 64 GB RAM | 79 TB Storage

    [Image: AIL4fc84QG6uSnTDEZiCCtosg7uAA8x9j1myFaFs...qL0Q=w2400]
    « Next Oldest | Next Newest »

    Users browsing this thread: 2 Guest(s)


    • View a Printable Version
    • Subscribe to this thread
    Forum Jump:

    Home · Team · Help · Contact
    © Designed by D&D - Powered by MyBB
    L


    Jellyfin

    The Free Software Media System

    Linear Mode
    Threaded Mode