2024-10-10, 05:19 PM
So the container is using port 8096, but that is not pushed to the host's interface without the "ports" section in your compose. Without "ports", only other containers on the same bridge will be able to access Jellyfin, which is OK if you are using NPM for all connections and NPM is on the same bridge network.
Having said that, I do believe you at least need "expose" on your jellyfin container so that NPM can connect on that port.
Having said that, I do believe you at least need "expose" on your jellyfin container so that NPM can connect on that port.
Code:
jellyfin-testing:
image: jellyfin/jellyfin:10.9.11
container_name: jellyfin-testing
hostname: jellyfin-testing
user: 1002:1002
group_add:
- "993" # Intel render group
networks:
blackmoon:
ipv4_address: 172.16.100.2
expose:
- 8096
volumes:
- ./jellyfin-stable-data/config:/config
- ./jellyfin-stable-data/cache:/cache
- /media/library:/media/library:ro
- /media/storage2:/media/storage2
- /media/ramdisk:/media/ramdisk
devices:
- /dev/dri/renderD128:/dev/dri/renderD128
environment:
- TZ=America/New_York
restart: unless-stopped