• Docker Network interface br0 gets removed when updating to 6.12.0 rc6, rc7 or rc8


    jimz011
    • Minor

    I have been running the prerelease versions for quite some time now and it usually doesn't really break a lot, however rc6,7 and 8 breaks my docker config. When I update it will update fine, but all containers that were configured to use a fixed IP with br0 are no longer working. The br0 option is gone from the dropdown in the docker config and when I stop/start docker it will throw errors that it can not create the socket.

    All other containers fail to autostart because of the few containers that use br0 won't start at all. Starting them manually works fine, however only containers that are in a docker network, bridge mode or host. All br0 containers will fail and when trying to start them it will throw an error like 'no such container'.

     

    I have even tried rebuilding the docker image by completely removing it and starting again, but that doesn't seem to fix the issue either.

     

    What have I tried?

    - Install RC6, RC7 and RC8 separately, with multiple reboots

    - Recreate docker image

    - Reinstall affected containers (but not possible to start because of missing ethernet interface)

     

    Reverting back to RC5 and everything works fine again (I have tried this a decent amount of times and RC5 will always work, whereas all newer RC's do not, I did get RC7 to work once, but once I stopped the docker service once it would remove the br0 interface again from docker config and throw the same errors).

     

    Not sure if this is a bug or that this was intentionally done, that is why I will report it here.




    User Feedback

    Recommended Comments

    It has been like this since Unraid 6.7 so wouldn't know what has changed. I will try to post diagnostics later on. I presume I need to post diagnostics from after the update and not from my current running version right?

     

    I also presume that diagnostics are found in the tools section?

    Link to comment
    23 minutes ago, jimz011 said:

    I presume I need to post diagnostics from after the update and not from my current running version right?

    yes

     

    23 minutes ago, jimz011 said:

    I also presume that diagnostics are found in the tools section?

    yes

    Link to comment

    I have the same or similar problem. All networks are gone with Docker since 6.12 which have ipv4 and ipv6 configured. Only the ones with ipv4 only are still there. 


    As a workaround I have manually configured the ipvlans. This works. 

     

    docker network create -d ipvlan \
        --subnet=xxx.xxx.32.0/20 --gateway=xxx.xxx.32.1 \
        --subnet=fd00:xxx:xxx::/64 --gateway=fd00:xxx:xxx:: \
        -o parent=br0 \
        -o ipvlan_mode=l2 cbr0


    Also on a new installation of Unraid the problem occurs.


    I have a bond (802.3ad) network as bridge with three network cards and still two network cards as bridge. These have a total of 5 vlans configured.

    As soon as I select ipv4 + ipv6 under "Settings/Network Settings" the networks are no longer created in docker. As long as they are pure ipv4 networks they are created in docker.


    If there is anything else you want me to try please let me know.

     

    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.