March 18, 201610 yr I decided to convert my cache drive file system from reiserfs to XFS. I copied the contents of my cache to another machine and then formatted the cache. I also upgraded the OS from 6.1.3 to 6.2 beta. Now, when I copy the contents of my cache drive back over, I'm having issues with Docker. When I direct it to read from the old docker.img file, it will not start up. If I let it create its own .img file, it's fine, but my user defined templates are gone so I have to download the dockers from scratch even though the appdata folder is already populated with all of the information it needs... Any idea what I might be doing wrong? I've noticed that the new system tries to point to a new "system" share, but I'm not sure if this could be the culprit.
March 18, 201610 yr Even using the user templates means you still have to download the actual app as appdata does not contain the application itself
March 19, 201610 yr Author If you're only on beta18 then upgrade to 6.2 beta 19. I am on 18. I will try 19. And I'm fine with redownlading the dockers. However, I want my configs, port mappings, etc., to remain the same from my last go around.
March 19, 201610 yr Author Tried 19, but I still get the same odd result. Docker storage location is set to /mnt/user/system/docker/docker.img. In that location is the old docker file I used back on 6.1.3. Status remains "stopped".
March 19, 201610 yr Tried 19, but I still get the same odd result. Docker storage location is set to /mnt/user/system/docker/docker.img. In that location is the old docker file I used back on 6.1.3. Status remains "stopped". I'm getting a bit confused by what you're referring to.... There are three parts to the docker "setup" [*]docker.img [*]appdata share [*]XML Files The docker.img can be deleted, and recreated, then you can use the XML files (stored on your flash) to add back your docker containers and as long as your appdata is still in the same place, you'll be back to where you want to be.
March 19, 201610 yr Community Expert Tried 19, but I still get the same odd result. Docker storage location is set to /mnt/user/system/docker/docker.img. In that location is the old docker file I used back on 6.1.3. Status remains "stopped". I'm getting a bit confused by what you're referring to.... There are three parts to the docker "setup" [*]docker.img [*]appdata share [*]XML Files The docker.img can be deleted, and recreated, then you can use the XML files (stored on your flash) to add back your docker containers and as long as your appdata is still in the same place, you'll be back to where you want to be. And to further clarify, the XML files stored on your flash are what is referred to as the "templates". These templates have all of your volume and port mappings. You can reselect them from the docker page from the dropdown. Any you have previously used are listed as "my-whatever". You can also reselect them from Community Applications with the Previous Apps button.
March 19, 201610 yr Author Tried 19, but I still get the same odd result. Docker storage location is set to /mnt/user/system/docker/docker.img. In that location is the old docker file I used back on 6.1.3. Status remains "stopped". I'm getting a bit confused by what you're referring to.... There are three parts to the docker "setup" [*]docker.img [*]appdata share [*]XML Files The docker.img can be deleted, and recreated, then you can use the XML files (stored on your flash) to add back your docker containers and as long as your appdata is still in the same place, you'll be back to where you want to be. And to further clarify, the XML files stored on your flash are what is referred to as the "templates". These templates have all of your volume and port mappings. You can reselect them from the docker page from the dropdown. Any you have previously used are listed as "my-whatever". You can also reselect them from Community Applications with the Previous Apps button. Well it looks like something is wrong with my docker.img file. I will have to recreate this. I misunderstood and thought that the templates (now I realize these are XML files) are stored on the flash! Thank you for the clarification. Where are the docker templates stored on the flash?
March 19, 201610 yr Community Expert Where are the docker templates stored on the flash? Depends on if you are going from the command line or from the network. On the network, your flash drive is the share named flash. From the command line, it is the folder named boot. Most of the things on your flash drive are readable text and it is worthwhile to explore it. Basically all of your configuration is stored there and it will make unRAID a lot less mysterious if you take a look. Knowing the above, I'll bet you can find the templates yourself.
March 19, 201610 yr Author Did something change on the paths from 6.1.3 to 6.2 b19? I copied over the template folder, and when selecting a user template I get this error: rning: simplexml_load_file(): /boot/config/plugins/dockerMan/templates-user/my-MariaDB.xml:1: parser error : Start tag expected, '<' not found in /usr/local/emhttp/plugins/dynamix.docker.manager/include/CreateDocker.php on line 231 Warning: simplexml_load_file(): ="31" /> in /usr/local/emhttp/plugins/dynamix.docker.manager/include/CreateDocker.php on line 231 Warning: simplexml_load_file(): ^ in /usr/local/emhttp/plugins/dynamix.docker.manager/include/CreateDocker.php on line 231 Basic View Template: /boot/config/plugins/dockerMan/templates-user/my-MariaDB.xml EDIT: I will answer my own question. Pretty sure the XML files I recovered from my accidental format are corrupt. Oh wellllllll, time to start over!
Archived
This topic is now archived and is closed to further replies.