• 6.12.4 - "Bad parameter" when starting docker after "New permissions" on cache pool

    ezhik

    By ezhik

      • Closed

    Re-pro steps:

     

    1. Create a cache pool, call it nvme-docker-vms

     

    2. configure shares: appdata and system -> set "Primary storage (for new files and folders)": nvme-docker-vms

     

    3. Docker Configuration:

    Settings -> Docker -> (Advanced View)

    Docker data-root: directory

    Docker directory: /mnt/user/system/docker

     

    3. Create and start dockers (more than 1)

     

    4. Stop dockers

     

    5. Go to Tools -> New Permissions -> Disks -> "nvme-docker-vms" -> START

     

    6. Go to Docker -> START ALL

     

    Expected:

    Dockers launch successfully

     

    Result:

    Dockers fail to start

     

    NOTE:

    When starting an individual docker an error is displayed: "Bad parameter"

     

    Workaround:

    1. Stop docker service

    2. Rename "docker" folder to "docker_old"

    mv /mnt/system/docker /mnt/system/docker_old

    3. Start docker

    4. Re-add dockers via saved [User templates] section in the 'Add docker' wizard

    Go to reports Stable Releases

    User Feedback

    Recommended Comments

    ChatNoir

    Not sure it's a bug.

    Running new permissions on appdata or the system share is not a good idea (especially if you are using docker with a directory rather than an image).

    Link to comment
    ezhik
    On 10/26/2023 at 2:07 AM, ChatNoir said:

    Not sure it's a bug.

    Running new permissions on appdata or the system share is not a good idea (especially if you are using docker with a directory rather than an image).


    I see. Shouldn't this be documented somewhere or may be as a guardrail be a warning that it can break things for Docker?

    Link to comment
    ezhik
    On 10/29/2023 at 3:06 PM, JorgeB said:

    You can use the FCP plugin docker safe new permissions tool, it doesn't touch the appdata folder.

    I think a technical control should be implemented here to account for docker presence. 

    Link to comment


    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.