July 18, 201510 yr I have been keeping an old docker around because I didn't want to break anything by changing the repository. I finally decided to move my dockers to the linuxserver ones and it was easier than I thought, so I documented it in case anyone else wants to do the same but is worried about doing it. [*]Stop current docker [*]Click docker icon and select edit on the current docker and take a screenshot of the current Volume Mappings [*]Click on docker icon and select Remove, at the prompt select "Container and Image" [*]Find the new version in Community Applications and click Add [*]Make sure volume mappings match your screenshot, change/add any that don't, then click Create [*]Done Something to bare in mind with the linuxserver docker is that after install it runs a script to fix user permissions that are set wrong, so if the webgui is not running this is probably why, it can anywhere between a few minutes and 20 or so minutes depending on the size of your library and speed of your server. If you aren't sure, go to the logs icon next to the docker container and click on it, if the last line is *** Running /etc/my_init.d/99_chown_plex_owned_files.sh... then the user script is still running.
July 19, 201510 yr Actually step 5 can be done even easier (no need to retype anything). Click Select a template -> under Templates User select the my-<template-name> to restore the settings.
July 19, 201510 yr Actually step 5 can be done even easier (no need to retype anything). Click Select a template -> under Templates User select the my-<template-name> to restore the settings. That would restore the original version. You would have to change the repository that the my* template brings up.
July 19, 201510 yr I quite often run two different sources of a docker with one lot of appdata to test. Just call one App-Repository1 App-Repository2 Easy Then when I've decided which one to use I delete the other and rename the winner App..
July 19, 201510 yr Author I quite often run two different sources of a docker with one lot of appdata to test. Just call one App-Repository1 App-Repository2 Easy Then when I've decided which one to use I delete the other and rename the winner App.. Not sure that is the greatest idea, as one docker can cause issues for another that you wouldn't necessarily be able to pin point to a certain docker. For example, the linuxserver plex docker doesn't have certain issues with permissions that are present in other dockers, running them off the same appdata folder would mean that both of them have issues with permissions. Of course the same is true starting with the one with issues and moving to the linuxserver one as it's not set up to correct issues it hasn't caused itself.
July 19, 201510 yr I quite often run two different sources of a docker with one lot of appdata to test. Just call one App-Repository1 App-Repository2 Easy Then when I've decided which one to use I delete the other and rename the winner App.. Not sure that is the greatest idea, as one docker can cause issues for another that you wouldn't necessarily be able to pin point to a certain docker. For example, the linuxserver plex docker doesn't have certain issues with permissions that are present in other dockers, running them off the same appdata folder would mean that both of them have issues with permissions. Of course the same is true starting with the one with issues and moving to the linuxserver one as it's not set up to correct issues it hasn't caused itself. Yeah, I see what you're saying and to be fair I haven't tried it with Plex, and I NEVER run both at the same time, but it helped to migrate things to linuxserver.io's containers and check they were working and it was invaluable when testing TVHeadEnd with different versions. Also very useful for testing stuff when I've added extra php stuff into my Apache docker. But I can see how someone could get into trouble with it.
July 19, 201510 yr Author Ahh, if they aren't running at the same time it's less of a problem, it's basically the same but you can move back to the old one if you have to.
July 19, 201510 yr Ahh, if they aren't running at the same time it's less of a problem, it's basically the same but you can move back to the old one if you have to. Yep, it's essentially just a bit more of a refined version of what you posted.. without the need for screenshots or anything. I open the config in one browser window, and the new config in a second browser window, copy and paste and ensure they are named differently.
February 16, 201610 yr Thanks to this post, I was able to move from LimTyech to Linux Plex docker. Awesome!
February 16, 201610 yr It seemed like a useful thing for the Docker FAQ, so I've added a FAQ entry there based on your post, Kode. Would you mind checking it out, let me know of any corrections or suggestions? Corrections and suggestions are welcome from anyone of course. I can't actually test it out myself at the moment.
March 14, 201610 yr I have been keeping an old docker around because I didn't want to break anything by changing the repository. I finally decided to move my dockers to the linuxserver ones and it was easier than I thought, so I documented it in case anyone else wants to do the same but is worried about doing it. [*]Stop current docker [*]Click docker icon and select edit on the current docker and take a screenshot of the current Volume Mappings [*]Click on docker icon and select Remove, at the prompt select "Container and Image" [*]Find the new version in Community Applications and click Add [*]Make sure volume mappings match your screenshot, change/add any that don't, then click Create [*]Done Something to bare in mind with the linuxserver docker is that after install it runs a script to fix user permissions that are set wrong, so if the webgui is not running this is probably why, it can anywhere between a few minutes and 20 or so minutes depending on the size of your library and speed of your server. If you aren't sure, go to the logs icon next to the docker container and click on it, if the last line is *** Running /etc/my_init.d/99_chown_plex_owned_files.sh... then the user script is still running. Thanks for posting the steps. I just completed them; but, when check the log file the last line is: Starting Avahi daemon Is this normal? It has been like this for almost 15 minutes now, nothing about the script mentioned above is in the log. Thanks in advance
March 16, 201610 yr Author iirc "Starting Avahi daemon" means it's finished so your webui should be accessible.
Archived
This topic is now archived and is closed to further replies.