Temp files for transcoding. No need to hit the disk.
Temp files for transcoding. No need to hit the disk.
This is how mine works, with a Nvidia GPU
services:
jellyfin:
volumes:
- jellyfin_config:/config
- jellyfin_cache:/cache
- type: tmpfs
target: /cache/transcodes
tmpfs:
size: 8G
- media:/media
image: jellyfin/jellyfin:latest
restart: unless-stopped
deploy:
resources:
reservations:
devices:
- driver: nvidia
device_ids:
- "0"
capabilities:
- gpu
I have tries the same on Ubuntu. It was also the desktop that had gotten removed, because if pipewire. Silly computer.
It’s from diskette. Not about what country the spelling is from.
No. You can leave that out. That was just me showing you that it runs on my machine, with that setup. Just bind the port instead.
Your passwords for the database does not match.
But the error is about it not being able to reach the database on the hostname.
I can run it with this compose file:
services:
jellystat-db:
image: postgres:16-alpine
container_name: jellystat-db
restart: unless-stopped
environment:
POSTGRES_USER: ${POSTGRES_USER}
POSTGRES_PASSWORD: ${POSTGRES_PASSWORD}
volumes:
- postgres-data:/var/lib/postgresql/data
networks:
- jellystat
jellystat:
image: cyfershepard/jellystat:latest
container_name: jellystat
restart: unless-stopped
environment:
POSTGRES_USER: ${POSTGRES_USER}
POSTGRES_PASSWORD: ${POSTGRES_PASSWORD}
POSTGRES_IP: jellystat-db
POSTGRES_PORT: 5432
JWT_SECRET: ${JWT_SECRET}
TZ: Europe/Paris # timezone (ex: Europe/Paris)
JS_BASE_URL: /
volumes:
- jellystat-backup-data:/app/backend/backup-data
depends_on:
- jellystat-db
networks:
- traefik
- jellystat
labels:
- traefik.enable=true
- traefik.docker.network=traefik
- traefik.http.routers.jellystat.entrypoints=https
- traefik.http.routers.jellystat.rule=Host(`${HOSTNAME}`)
- traefik.http.routers.jellystat.tls.certresolver=http
- traefik.http.routers.jellystat.service=jellystat
- traefik.http.services.jellystat.loadbalancer.server.port=3000
- traefik.http.services.jellystat.loadbalancer.server.scheme=http
networks:
jellystat: {}
traefik:
external: true
volumes:
postgres-data: null
jellystat-backup-data: null
In the same place as you run your docker compose up
command you just type docker compose logs
There will probably be something in the logs that tells you what is going wrong. Maybe it can’t connect to the db, or maybe it’s starting on a wrong port or something.
Uh! They should use AI for it. That will be great! /s
They have a docker-compose.yml
file in the repo. It looks like it has everything all ready for you.
Ah - a Tesla, I assume :)
Hmm. I would think so. But I haven’t actually checked. That was my thought.