Jump to content
  • [6.12.4] Docker settings path with leading space ' ' is allowed but cause dockers to be empty on each reboot


    Alex R. Berg
    • Minor

    I had a leading space in my 'Docker vDisk location:', which caused the docker image to be located on root / in a directory called ' ' (space). Since root is memory, it empty on each reboot. It was quite difficult for me to figure out that was the file being written. 

    It is easy to get into that situation, just stop the docker, add a leading space, and apply and enable docker. 

    It is difficult to get out of the situation because the GUI will not let me remove the space or change it to a valid location, UNLESS i use the GUI folder popup navigation. If I click my way to the correct folder then the GUI updates the location. 

    I suspect the issue surfaced after i changed my docker image to be located on an external USB mounted with unassigned devices. 

    Background: I'm running a QNAP hardware with unRaid, I don't have room for SSD, and don't want disks spinning up. Hence plugged in an extra USB, used unassigned devices (thank you devs) to auto-mount usb, and moved the docker image there.
    ---
    So my suggestion is to do a simple trim of the path on apply. Or something like that. 




    User Feedback

    Recommended Comments

    There are no comments to display.



    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Guest
    Add a comment...

    ×   Pasted as rich text.   Restore formatting

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.


  • Status Definitions

     

    Open = Under consideration.

     

    Solved = The issue has been resolved.

     

    Solved version = The issue has been resolved in the indicated release version.

     

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

    Retest = Please retest in latest release.


    Priority Definitions

     

    Minor = Something not working correctly.

     

    Urgent = Server crash, data loss, or other showstopper.

     

    Annoyance = Doesn't affect functionality but should be fixed.

     

    Other = Announcement or other non-issue.

×
×
  • Create New...