• Unraid docker dont recognize subnet mask 30

    • Minor

    I got latest stable unraid installation. Three networks connected to Unraid. 

    first without vlan tag unbridged eth0 for main connection to server with subnet , in routing table everythings fine its apears as route

    For docker containers a setup outside network with vlan tags

    First network for container  is  and second  so should be available hosts for docker networks and

    Networks appear in docker containers when i try to edit them as Custom eth0.48, and eth0.49 then i setup and address respectively or . But  when I press an Apply it show me no address pool available and docker creation failed. So i started to dig and noticed that in unraid networks routingtable  routes appears and  with gateways where is correct and no routes with and . I tried with another subnets like 29 , and everything works as should.

    In screenshots can be seen that






    User Feedback

    Recommended Comments

    Same error if i leave empty or add pool. In fact it didn't change anything 

    Edited by ingux16
    Link to comment

    The error message comes from Docker, it can’t reserve any addresses for its own internal dhcp service.


    Instead of assigning a fixed .2 address, leave it open and let docker assign the address automatically (dhcp). See if that works.


    Side note: assigning /30 networks isn’t really practical here.

    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.