Issues launching docker containers after upgrading to 5

  • Hello, I am opening a new ticket to track a problem that I had after upgrading. It spawned out of this ticket.


    The current problem I have is that my docker containers are not finding the configurations that I had when I originally created them in 4. When I created them in 4 I used the practice of putting the configurations in /sharedfolders/AppData/<program name>.


    For example, in SABNZBD it started me from the beginning as if it was a first-time run. In the Portainer UI I can clearly see that the /config path is the /sharedfolder/AppData/Sabnzbd (and all of my other settings are there) but when I went through the wizard it did not update that file. I know that it created somewhere because the basic settings that I had entered in the wizard had in fact saved. If I open up the container folder that portainer shows I can see that the two .json files have new timestamps and have all of my original configuration in them. However, the app is clearly looking somewhere else for the sabnzbd.ini file. I did a search on sabnzbd.ini and could not find it anywhere other than AppData. I have similar experience in the other containers I have tried. Any ideas how to debug this?



    Here is a screen cap from portainer. This is my original config from when I created it in 4.

    • Official Post

    Seems like you have three options:

    1. change the paths in Portainer from /sharedfolder/xxx to the correct absolute path like /srv/dev-disk-by-uuid-......
    2. create symlinks in a folder /sharedfolders/ pointing at the shared folders on the data drives
    3. re-enable the /sharedfolders" feature
  • Seems like you have three options:

    1. change the paths in Portainer from /sharedfolder/xxx to the correct absolute path like /srv/dev-disk-by-uuid-......
    2. create symlinks in a folder /sharedfolders/ pointing at the shared folders on the data drives
    3. re-enable the /sharedfolders" feature

    Thank you so much for that. Just to be clear, I had created a folder called "sharedfolders". I did not even realize there was some kind of separate service for this?

    Anyway, I went into the SABNzbd container and I see config.v2.json and hostconfig.json. Inside of each of those files I see references to the config being in the "sharedfolders" path - I quickly changed them to use the /srv path, saved them, and then verified that the changes took. I restarted sabnzbd and the values were changed back to use the sharedfolder path for the config. I don't know how to proceed.

  • Post docker inspect <name_of_the_container>


    Blank sensible information like passwords.


    And please explain, why ti is not possible to read out the config to a dockerfile as mentioned in the other thread. Post the error message. This is the most promising way.

    If you got help in the forum and want to give something back to the project click here (omv) or here (scroll down) (plugins) and write up your solution for others.

  • Post docker inspect <name_of_the_container>


    Blank sensible information like passwords.


    And please explain, why ti is not possible to read out the config to a dockerfile as mentioned in the other thread. Post the error message. This is the most promising way.


    Sure, I've included the sabnzbd info below.


    I am sorry, I am not completely sure what you mean about reading out the config of the dockerfile.


  • There should be your config: ls -l /sharedfolders/AppData/SABNzbd/config


    How do you define the containers? docker command from cli, portainer containers, portainer stacks or docker-compose?


    If you need a docker-compose.yml file or a portainer stack from an existing container run this:

    docker run --rm -v /var/run/docker.sock:/var/run/docker.sock ghcr.io/red5d/docker-autocompose SABNzbd

    If you got help in the forum and want to give something back to the project click here (omv) or here (scroll down) (plugins) and write up your solution for others.

  • Again, thank you so much for all of your help here. While debugging this I thought I was looking in the /sharedfolders directory when I was actually looking in the /srv path for the config. At some point the config in sharedfolders/../AppData was re-initialized. I had the original config files in /srv/../ApData. When I copied over the config files form the latter to the former the containers were loaded with the correct config.

  • Go to clean it up, Create a symlink and use that for the config, do not mix /srv/dev-... pathes and /sahredfolers/... pathes.

    If you got help in the forum and want to give something back to the project click here (omv) or here (scroll down) (plugins) and write up your solution for others.

  • Go to clean it up, Create a symlink and use that for the config, do not mix /srv/dev-... pathes and /sahredfolers/... pathes.

    Right - is there any reason that I just can't go back to using the /sharedfolders path for the config? I think that I only tried creating the config in /srv path because I was having permission problems.

  • No, but you have to remember, that it is a link, not a bind mount as it was before (if i remember correctly)

    If you got help in the forum and want to give something back to the project click here (omv) or here (scroll down) (plugins) and write up your solution for others.

  • muchgooder

    Added the Label resolved

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!