2024-12-14, 10:55 PM
(2024-12-12, 01:52 PM)TheDreadPirate Wrote: That is not strictly necessary, since the cache folder is temporary data. But you can if you want. You can move files around anywhere you want on the host side, as long as you provide that new path to the container.
Okay, so, the best way I thought to accomplish this was to remove the docker Jellyfin container and completely rebuild it with a docker compose file. It seems to have worked. Portainer is showing a container named Jellyfin with the correct config and cache paths, but now, I cannot reach Jellyfin on my local network. Here is the docker compose file:
Code:
services:
jellyfin:
image: jellyfin/jellyfin
container_name: jellyfin
user: 1000:1000
network_mode: 'host'
volumes:
- /config:/config
- /cache:/cache
- type: bind
source: /media/danielle/library/Movies
target: /Movies
- type: bind
source: /media/danielle/library/Shows
target: /Shows
read_only: true
restart: 'unless-stopped'
But https://jellyfin.local and the address of my server with port 8096 gives me "This site can't be reached". Do I need to change the network_mode in the docker-compose.yml to the port? In the past, I know that worked, but I'm not sure why.
Rescued from the Trash Optiplex Build
CPU: Intel i5 3470
RAM: 4GB DDR3-1333
GPU: NVIDIA Quadro P400 2GB GDDR5
Boot Drive: Inland Professional 240GB SSD
Storage: Seagate Ironwolf 8TB 7200 RPM HDD
CPU: Intel i5 3470
RAM: 4GB DDR3-1333
GPU: NVIDIA Quadro P400 2GB GDDR5
Boot Drive: Inland Professional 240GB SSD
Storage: Seagate Ironwolf 8TB 7200 RPM HDD