Closed vegedb closed 2 years ago
Thanks for opening your first issue here! Be sure to follow the issue template!
There is nothing confusing about it. Our latest
is built from their stable repo and our nightly
is built from their unstable repo. They are both listed in our readme.
The docker hub images are all tagged with the upstream version numbers as they appear in their repos.
Their release candidates are not in any of their repos therefore we won't be building them.
@aptalca I see that's a shame. I have an issue changing to the official container (RC). It simply doesn't read my previous library (config,cache) made using linuxserver. I only changed the image to jellyfin/jellyfin from linuxserver/jellyfin.
How do you convert linuxserver to the official container?
Switching between our and others' images is not something we support. You should probably set up a fresh instance of the other container, compare their persistent folder structure to ours and make any necessary changes. But that's about the extent of the support we can provide.
As far as I can see there's no issue on the volumes as they are the exact same. I can docker exec bash and see the folders/contents are there. I'm stuck.
I'm also trying to migrate right now.
Current issue from what I understand is I mounted the config directory for the linuxserver image like so:
- /storage/containers/jellyfin/config:/config
10.6.x
/storage/containers/jellyfin/config$ ls -la
total 68
drwxr-xr-x 8 ubuntu ubuntu 4096 Dec 3 11:31 .
drwxr-xr-x 4 ubuntu ubuntu 4096 Jul 7 13:13 ..
drwxr-xr-x 2 ubuntu ubuntu 4096 Dec 4 20:04 ScheduledTasks
-rw-r--r-- 1 ubuntu ubuntu 251 Nov 30 11:12 branding.xml
drwxr-xr-x 8 ubuntu ubuntu 4096 Dec 4 20:49 cache
drwxr-xr-x 7 ubuntu ubuntu 4096 Aug 6 19:29 data
drwxr-xr-x 4 ubuntu ubuntu 4096 Jul 7 13:14 dlna
-rw-r--r-- 1 ubuntu ubuntu 1132 Dec 5 19:08 encoding.xml
drwxr-xr-x 2 ubuntu ubuntu 4096 Dec 6 00:00 log
-rw-r--r-- 1 ubuntu ubuntu 1362 Jul 7 13:14 logging.default.json
-rw-r--r-- 1 ubuntu ubuntu 243 Nov 19 11:42 metadata.xml
-rw-r--r-- 1 ubuntu ubuntu 1333 Aug 2 13:42 migrations.xml
-rw-r--r-- 1 ubuntu ubuntu 236 Aug 6 21:11 playback_reporting.xml
-rw-r--r-- 1 ubuntu ubuntu 6768 Dec 3 10:56 system.xml
drwxr-xr-x 7 ubuntu ubuntu 4096 Jul 16 15:00 users
-rw-r--r-- 1 ubuntu ubuntu 445 Dec 3 17:54 xbmcmetadata.xml
But it appears the folder structure is different for the jellyfin image: stable-rc (not fresh install)
/storage/containers/jellyfin-broken/config$ ls -la
total 92
drwxr-xr-x 12 ubuntu ubuntu 4096 Dec 6 13:15 .
drwxr-xr-x 4 root root 4096 Jul 7 13:13 ..
drwxr-xr-x 2 ubuntu ubuntu 4096 Dec 4 20:04 ScheduledTasks
-rw-r--r-- 1 ubuntu ubuntu 251 Nov 30 11:12 branding.xml
drwxr-xr-x 8 ubuntu ubuntu 4096 Dec 4 20:49 cache
drwxr-xr-x 3 root root 4096 Dec 6 13:15 config
drwxr-xr-x 9 ubuntu ubuntu 4096 Dec 6 13:15 data
drwxr-xr-x 4 ubuntu ubuntu 4096 Jul 7 13:14 dlna
-rw-r--r-- 1 ubuntu ubuntu 1132 Dec 5 19:08 encoding.xml
drwxr-xr-x 2 ubuntu ubuntu 12288 Dec 6 13:19 log
-rw-r--r-- 1 ubuntu ubuntu 1362 Jul 7 13:14 logging.default.json
drwxr-xr-x 2 root root 4096 Dec 6 13:14 metadata
-rw-r--r-- 1 ubuntu ubuntu 243 Nov 19 11:42 metadata.xml
-rw-r--r-- 1 ubuntu ubuntu 1333 Aug 2 13:42 migrations.xml
-rw-r--r-- 1 ubuntu ubuntu 236 Aug 6 21:11 playback_reporting.xml
drwxr-xr-x 3 root root 4096 Dec 6 13:15 plugins
drwxr-xr-x 3 root root 4096 Dec 6 13:15 root
-rw-r--r-- 1 ubuntu ubuntu 6768 Dec 3 10:56 system.xml
drwxr-xr-x 7 ubuntu ubuntu 4096 Jul 16 15:00 users
-rw-r--r-- 1 ubuntu ubuntu 445 Dec 3 17:54 xbmcmetadata.xml
Notice the config
folder in there.
/storage/containers/jellyfin-broken/config/config$ ls
dlna encoding.xml logging.default.json migrations.xml network.xml system.xml
This is not a clean install it was an attempt at migrating. Some files are moved in their own config folder.
To migrate, assuming you have a volume mounted like so:
/storage/jellyfin/config:/config
/storage/jellyfin/cache:/cache
(I know above I have a containers/ folder I just forgot to put it down here, doesn't change much for ya)
Stop the container I should have also maybe disabled the plugins as they caused some errors at startup after upgrade but, well.
Create a backup:
tar -cv -I 'xz -8 -T0' -f /storage/jellyfin-old.tar.xz /storage/jellyfin
Go to /storage/jellyfin/config
All commands must be typed from there.
mkdir config
mv encoding.xml logging.default.json metadata.xml migrations.xml system.xml branding.xml dlna ./config
mv ./data/metadata ./metadata
mv ./data/root ./root
mv ./data/transcodes ./transcodes
mv ./data/plugins ./plugins
mv ./data/data ./data2
# go to ./data and make sure it's empty, no left over files. my install didn't have anything else there so I deleted it
rmdir ./data
mv ./data2 ./data
mv ./ScheduledTasks ./data/ScheduledTasks
mv ./cache ../
# NOT SURE if they go there but whatever, probably :laughing:
mv xbmcmetadata.xml playback_reporting.xml ./config
Change image:linuxserver/jellyfin:latest
to image:jellyfin/jellyfin:stable-rc
Start the container.
Worked for me, all users are there and my progress too. I didn't test plugins yet but it should work also.
If you messed up, or I messed up - remove jellyfin folder and extract your backup:
rm -rf ./jellyfin
tar -xf jellyfin-old.tar.xz ./jellyfin
@vegedb
EDIT: Intros and Skin Manager were broken, I had to remove and reinstall them.
@aptalca The RC release is in the jellyfin repo: https://github.com/jellyfin/jellyfin/releases/tag/v10.7.0-rc1
Or did you mean something else?
@Extarys I'm referring to the debian/ubuntu package repos
To migrate, I just had to define these variables in my docker compose :
- JELLYFIN_DATA_DIR=/config/data
- JELLYFIN_CONFIG_DIR=/config
- JELLYFIN_LOG_DIR=/config/log
- JELLYFIN_CACHE_DIR=/config/cache
@faizpuru Yeah I had to restore my backup and do the same. Some paths are hardcoded into the database for each file in a BLOB column, which make it very difficult to change.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
RC1
Here is the quote,
Hope you change to their naming convention, I'm totally confused as to which is which in your dockerhub