Jump to content

  • Docker Network bug after restart

    JamesAdams

    By JamesAdams

      • Annoyance

    Hi,

     

    i founs a bug in Docker, to reproduce it you must have created a virtual network with virsh.

     

    like that :

    Quote

    docker network create \
    -o parent=virbr1-lab \
    --driver macvlan \
    --subnet 192.168.0.0/24 \
    --gateway 192.168.0.10 \
    docker-lab0

     

    And you have to create a network in docker.

     

    Like that :

    Quote

    docker network create \
    -o parent=virbr1-lab \
    --driver macvlan \
    --subnet 192.168.0.0/24 \
    --gateway 192.168.0.10 \
    docker-lab0

     

    for the moment everything works without problem but if you restart the unraid server or you restart docker

     

    When you want to restart your container it will tell you that the network docker-lab0 with the ip "8c ..." cannot be found even though it does exist and its id has not changed...


     

    Quote

     

    Error response from daemon: failed to create endpoint 79bb6b95-bd76-469c-bd76-baf92c491b65 on network docker-lab0: network id "8c0e37126a3623e62cc8d91a6b2f11620c4f61754ee9af22748f03c1bf0c8cdf" not found


    Error: failed to start containers: 79bb6b95-bd76-469c-bd76-baf92c491b65

     

     

    Cordially.

     

     

    Go to reports Stable Releases

    User Feedback

    Recommended Comments

    JamesAdams

    the error is indeed due to the fact that the docker network has as its parent the virtual network virsh because if I remove it the option 

    Quote

    -o parent=virbr1-lab \

    it's working

    Link to comment
    tjb_altf4

    Unraids implementation of docker doesn't preserve user defined networks between restarts unless you explicitly enable the option to do so.  This can be done in docker settings while docker service is disabled.

    Link to comment
    JamesAdams

    I think I found a clue of the problem and it would come from auto start from docker to starting Unraid because if I stop docker with /etc/rc.d/rc.docker stop and restart it with /etc/rc.d/rc.docker start it works perfectly

    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.

×
×
  • Create New...