Jump to content
  • [6.10.-RC4] Problems with Docker start/stop

    • Minor

    Since 6.10-RC4 I experience daily problems with the docker system. Sometimes a docker container does not stop, sometimes a docker container does not start. In my user script backup, that is running every night since years, I do something like that for every container:


    docker stop <containername>
    rsync -avPX --delete-during /mnt/<poolname>/system/appdata/<containername>/ /mnt/disk1/Backup/Tower/system/appdata/<containername>/
    docker start <containername>


    In the case of an error, the backup user script returns something like that:


    Error response from daemon: cannot stop container: <containername>: tried to kill container, but did not receive an exit event


    This results in backups not taken correctly, because of a container that's still running, or in containers that did not restart. Usually it helps to repeat that same commands on the command line to bring the system back to it's normal state. But these are manual steps that have to be done every morning currently.


    In syslog I do see lots of docker related lines.


    Diagnostics attached.


    Thanks a lot.



    User Feedback

    Recommended Comments

    I'm also having this problem, except nothing helps. How do I restart the docker service without restarting UnRAID entirely?

    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.

    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...