• [6.12.0/6.12.1/6.12.2] - DOCKER - Dockers can't start (after 3-4 days running)

    Pducharme

    By Pducharme

      • Solved Urgent

    Hi, I would like to report a Bug with the Official 6.12.0 / 6.12.1 version.

     

    SInce the 6.12.x beta + rc, it seems that there is some kind of memory leak or similar, that make Docker not working properly until a full Reboot occurs.   The issue can be reproduce easily :

     

    1. Boot Unraid 6.12

    2. Start all your dockers 

    3. Wait (randomly 3-4-5 days, never same amount of time)

    4. Update a docker, and it will not be able to start, throwing a "Execution Error" / "Server Error".

     

    Once you start getting this error, you won't be able to restart ANY dockers you have running (it will throw the same error).

    You can't even disable Docker, then Re-enable Docker, it just fail.   

    A full server reboot will fix it for 3-4-5 more days, then it will come back.

     

    Another observation, I'm running "homepage" docker, and it sees the "health" of "PlexMediaServer" docker.  When the bug isn't triggered yet (during the first days after a reboot), it reports the health of PlexMediaServer to be "healthy", but once the bug is happening, even without restarting a docker, the homepage docker report "Unhealthy" for Plex.  At that point, I know I need to reboot.  I confirmed by trying restarting any docker, and got the "Execution Error" every single time that the Plex is shown as "unhealthy".

     

    Hopefully, this bug report will get some traction.  If you haven't seen it yet, I suppose it's a question of days before it happens.

     

    I see that i'm not alone with this bug (see :  https://forums.unraid.net/topic/140301-unraid-612-rc7-docker-stops-after-update/#comment-1274038 )

    • Like 1
    • Upvote 1
    Go to reports Stable Releases

    User Feedback

    Recommended Comments



    Pducharme

    @Peuuuur Noel Can you update your NVIDIA plugins?  The default Logging Level was modified to "warning" instead of "info".  In combination with Unraid 6.12.2.  I bet you could leave the "health monitoring" activated.  I'm currently testing it like that :  6.12.2, latest NVIDIA Plugins, latest Driver, default Healty Monitoring (meaning i didn't add --no-healthcheck).  Will probably be a lot more stable.  I think that they can probably revert to latest Docker Engine like they had in 6.12.0 and 6.12.1...

     

    For anyone else having this issue, are you running the Official PLEX Inc Docker combined with a NVIDIA GPU that you use in the Docker?

     

    Link to comment
    erak
    3 minutes ago, Pducharme said:

    For anyone else having this issue, are you running the Official PLEX Inc Docker combined with a NVIDIA GPU that you use in the Docker?

     

    Yes I am.

    Link to comment
    Peuuuur Noel
    9 minutes ago, Pducharme said:

    @Peuuuur Noel Can you update your NVIDIA plugins?  The default Logging Level was modified to "warning" instead of "info".  In combination with Unraid 6.12.2.  I bet you could leave the "health monitoring" activated.  I'm currently testing it like that :  6.12.2, latest NVIDIA Plugins, latest Driver, default Healty Monitoring (meaning i didn't add --no-healthcheck).  Will probably be a lot more stable.  I think that they can probably revert to latest Docker Engine like they had in 6.12.0 and 6.12.1...

     

    For anyone else having this issue, are you running the Official PLEX Inc Docker combined with a NVIDIA GPU that you use in the Docker?

     

     

    I updated my Nvidia plugin 2 hours ago and no more nvidia runtime info in logs (--no-healthcheck removed from container).

    Edited by Peuuuur Noel
    Link to comment
    sithlordmike90

    I was also having this issue and have been checking up on the posts regularly. Having just ticked over 2 full days uptime with the new nvidia gpu plugin update I can happily report I still have not encountered any issues, first time since the 6.12.1 update I've made it over 2 days!

    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.