• Docker - "Host access to custom networks" needs to be re-enabled after crash

    • Annoyance

    I have Host access to custom networks: enabled in my Docker settings.

    Started from 6.9.1 I began to get regular crashes where I need to power off/on my Unraid server. Whenever this happens everything starts up as expected and parity check begins.

    Docker containers set to autostart will start, but I'm not able to connect between containers. I have to stop all containers, go to Docker settings, disable Docker and re-enable docker to "re-apply" Host access to custom networks-setting.



    User Feedback

    Recommended Comments

    Can confirm a bad poweroff/restart through watchdog on IPMI or a loss of power causes this for me as well. I've been experiencing it since pre 6.9. Afterwards I cannot ping any docker with a custom IP from the unraid server BUT they can be reached from non unraid devices on the network.


    Soft/Graceful reboot gives no issue.

    Link to comment

    Just to add I've spent a considerable time today trying to figure out why Plex could no longer communicate with tvhproxy, turns out this bug is the reason.


    I did a reboot of unRAID and all started working again.


    This should have a priority of Minor at least, not Annoyance as functionality is affected.

    Edited by fireplex
    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.