Skip to content

Update container.md #1392

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
+3 −0
Open

Update container.md #1392

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions docs/general/installation/container.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -173,6 +173,9 @@ Steps to run Jellyfin using Podman are similar to the Docker steps.
--label "io.containers.autoupdate=registry" \
--name myjellyfin \
--publish 8096:8096/tcp \
--publish 8920:8920/tcp \
--publish 1900:1900/udp \
Copy link
Member

@felix920506 felix920506 Apr 27, 2025 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

for DLNA to work, host networking is required, which makes forwarding port 1900 redundant

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The instructions provide two different examples of how to start a container. The first using a docker compose file does include the host option but the second one does not. It specifically only maps 8096 which seems to block everything else.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As seen here:

serveradmin@jellyfin:~/podman/jellyfin$ podman run -d -p 8096:8096/tcp -u $(id -u):$(id -g) --label "io.containers.autoupdate=registry" --name jellyfin --rm --userns keep-id --volume /home/serveradmin/podman/jellyfin/cache:/cache:Z --volume /home/serveradmin/podman/jellyfin/config:/config:Z --mount type=bind,source=/home/serveradmin/podman/jellyfin/media,destination=/media,ro=false,relabel=private docker.io/jellyfin/jellyfin:latest
852e320cdf4e897c1072f0d29bb6b3b817bb6c92562bd7eb05be644097d3c79d

serveradmin@jellyfin:~/podman/jellyfin$ podman port jellyfin
8096/tcp -> 0.0.0.0:8096

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would prefer to have host networking be the default, since some features require it.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The docker section uses host mode in the listed example command for reference

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The current "podman run" example does not use host mode thus the need to open the autodiscovery ports.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

https://docs.podman.io/en/stable/markdown/podman-run.1.html
"host: Do not create a network namespace, the container uses the host’s network. Note: The host mode gives the container full access to local system services such as D-bus and is therefore considered insecure."

--publish 7359:7359/udp \
--rm \
--user $(id -u):$(id -g) \
--userns keep-id \
Expand Down