2024-11-09, 05:56 PM
(This post was last modified: 2024-11-09, 06:05 PM by TheYang. Edited 2 times in total.)
Hey, it's not started with systemctl, it's an (old) self-made docker container which probably uses most bad-practices out there, but it did work!
it's started with an entrypoint that just starts jellyfin on boot
jellyfin --webdir /usr/share/jellyfin/web/ --ffmpeg /usr/share/jellyfin-ffmpeg/ffmpeg
but to answer your question:
sudo systemctl status jellyfin
sudo: systemctl: command not found
I've not migrated because I didn't want to lose the userdata and didn't want to re-make the database either (and didn't succeed in trying to transfer it). Oh and space constraints for the database were there as well (because I want that on an SSD, so I couldn't have two databases built and then migrate from one container to the other)
it's started with an entrypoint that just starts jellyfin on boot
jellyfin --webdir /usr/share/jellyfin/web/ --ffmpeg /usr/share/jellyfin-ffmpeg/ffmpeg
but to answer your question:
sudo systemctl status jellyfin
sudo: systemctl: command not found
I've not migrated because I didn't want to lose the userdata and didn't want to re-make the database either (and didn't succeed in trying to transfer it). Oh and space constraints for the database were there as well (because I want that on an SSD, so I couldn't have two databases built and then migrate from one container to the other)