Jump to content

Problem with unraid server disapearing from Network when Dockers are enabled

Natas

By Natas
in General Support

Go to solution Solved by Squid,

Recommended Posts

Natas Noob

Natas

Posted
Posted

I am having this issues with 6.10.0-rc2 and 6.10.0-rc3

 

When Dockers are disabled, I can see \\Tower on the Network and access it at all times.

 

When Dockers are enabled, my unraid server disappear from the Network, but I can still access it with \\Tower. If I change the permissions on a User Share, my Server will appear on the Network for a few minutes and then disappear again.

 

I need Dockers enabled and I need to see my Unraid server on the Network at the same time. This problem never happened in version 6.9.2.

Link to comment
Natas Noob

Natas

Posted
  • Author
Posted (edited)
21 minutes ago, ChatNoir said:

Please attach your diagnostics.

 

What dockers are you running ?

 

Did you try to stop all dockers and start them up one at a time (with a few minutes in between) to see if it is related to one docker specifically ?

I am running these tests with no Dockers at all. Just starting the Docker service causes this problem.

Edited by Natas
Link to comment
ChatNoir Experienced

ChatNoir

Posted
Posted
17 hours ago, Natas said:

I am running these tests with no Dockers at all. Just starting the Docker service causes this problem.

 

Did you reinstall dockers ? Because I see several dockers, some that don't seem functional. 

Mar 12 14:26:29 NAS avahi-daemon[6021]: Joining mDNS multicast group on interface docker0.IPv4 with address 172.17.0.1.
Mar 12 14:26:29 NAS avahi-daemon[6021]: New relevant interface docker0.IPv4 for mDNS.
Mar 12 14:26:29 NAS avahi-daemon[6021]: Registering new address record for 172.17.0.1 on docker0.IPv4.
Mar 12 14:26:30 NAS avahi-daemon[6021]: Server startup complete. Host name is NAS.local. Local service cookie is 2913227390.
Mar 12 14:26:30 NAS rc.docker: created network br0 with subnets: 192.168.1.0/24; 
Mar 12 14:26:31 NAS rc.docker: binhex-plex: Error response from daemon: error gathering device information while adding custom device "/dev/dri": no such file or directory
Mar 12 14:26:31 NAS rc.docker: Error: failed to start containers: binhex-plex
Mar 12 14:26:31 NAS rc.docker: pihole: Error response from daemon: network 37d4b1ed9aca4739dadda1706954d6198f42c11a9210c8fe4aebca228089548e not found
Mar 12 14:26:31 NAS rc.docker: Error: failed to start containers: pihole
Mar 12 14:26:31 NAS kernel: docker0: port 1(veth406115d) entered blocking state
Mar 12 14:26:31 NAS kernel: docker0: port 1(veth406115d) entered disabled state
Mar 12 14:26:31 NAS kernel: device veth406115d entered promiscuous mode
Mar 12 14:26:31 NAS kernel: docker0: port 1(veth406115d) entered blocking state
Mar 12 14:26:31 NAS kernel: docker0: port 1(veth406115d) entered forwarding state
Mar 12 14:26:31 NAS kernel: docker0: port 1(veth406115d) entered disabled state
Mar 12 14:26:31 NAS kernel: eth0: renamed from vethda82210
Mar 12 14:26:31 NAS kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth406115d: link becomes ready
Mar 12 14:26:31 NAS kernel: docker0: port 1(veth406115d) entered blocking state
Mar 12 14:26:31 NAS kernel: docker0: port 1(veth406115d) entered forwarding state
Mar 12 14:26:31 NAS kernel: IPv6: ADDRCONF(NETDEV_CHANGE): docker0: link becomes ready
Mar 12 14:26:31 NAS rc.docker: qbittorrent: started succesfully!

 

Could it be an issue with pihole ?

 

Not a network expert, but I think that I see several IP ranges and several subnets. Is that expected ?

You might want to check if every thing is OK with your router and maybe get back to a simpler architecture temporarily to see if it works and redo the steps ?

 

Hopefully someone with more knowledge in networking and docker can chime in.

Link to comment
Natas Noob

Natas

Posted
  • Author
Posted (edited)
8 hours ago, ChatNoir said:

 

Did you reinstall dockers ? Because I see several dockers, some that don't seem functional. 

Mar 12 14:26:29 NAS avahi-daemon[6021]: Joining mDNS multicast group on interface docker0.IPv4 with address 172.17.0.1.
Mar 12 14:26:29 NAS avahi-daemon[6021]: New relevant interface docker0.IPv4 for mDNS.
Mar 12 14:26:29 NAS avahi-daemon[6021]: Registering new address record for 172.17.0.1 on docker0.IPv4.
Mar 12 14:26:30 NAS avahi-daemon[6021]: Server startup complete. Host name is NAS.local. Local service cookie is 2913227390.
Mar 12 14:26:30 NAS rc.docker: created network br0 with subnets: 192.168.1.0/24; 
Mar 12 14:26:31 NAS rc.docker: binhex-plex: Error response from daemon: error gathering device information while adding custom device "/dev/dri": no such file or directory
Mar 12 14:26:31 NAS rc.docker: Error: failed to start containers: binhex-plex
Mar 12 14:26:31 NAS rc.docker: pihole: Error response from daemon: network 37d4b1ed9aca4739dadda1706954d6198f42c11a9210c8fe4aebca228089548e not found
Mar 12 14:26:31 NAS rc.docker: Error: failed to start containers: pihole
Mar 12 14:26:31 NAS kernel: docker0: port 1(veth406115d) entered blocking state
Mar 12 14:26:31 NAS kernel: docker0: port 1(veth406115d) entered disabled state
Mar 12 14:26:31 NAS kernel: device veth406115d entered promiscuous mode
Mar 12 14:26:31 NAS kernel: docker0: port 1(veth406115d) entered blocking state
Mar 12 14:26:31 NAS kernel: docker0: port 1(veth406115d) entered forwarding state
Mar 12 14:26:31 NAS kernel: docker0: port 1(veth406115d) entered disabled state
Mar 12 14:26:31 NAS kernel: eth0: renamed from vethda82210
Mar 12 14:26:31 NAS kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth406115d: link becomes ready
Mar 12 14:26:31 NAS kernel: docker0: port 1(veth406115d) entered blocking state
Mar 12 14:26:31 NAS kernel: docker0: port 1(veth406115d) entered forwarding state
Mar 12 14:26:31 NAS kernel: IPv6: ADDRCONF(NETDEV_CHANGE): docker0: link becomes ready
Mar 12 14:26:31 NAS rc.docker: qbittorrent: started succesfully!

 

Could it be an issue with pihole ?

 

Not a network expert, but I think that I see several IP ranges and several subnets. Is that expected ?

You might want to check if every thing is OK with your router and maybe get back to a simpler architecture temporarily to see if it works and redo the steps ?

 

Hopefully someone with more knowledge in networking and docker can chime in.

This diagnostic was one of the first thing I did after reassigning my drives on the fresh install. I disabled the docker service and deleted docker.img afterward. The problem is still there even with an empty docker.img (which means no dockers at all)

Edited by Natas
Link to comment
Natas Noob

Natas

Posted
  • Author
Posted (edited)

I have factory reset my router to see if there could be a problem between these two, which I highly doubted there could be but I did it anyway. After the factory reset, Unraid still disappear from the network after I start the docker service (with no installed dockers)

 

I have attached a disgnostics file right after I rebooted the server with the docker service enabled.

 

This is what I did : Deleted docker.img, restarted the server with dockers enabled. Waited for the server to restart and for the docker service to start. once I saw that the server disapeared from the network, I stopped the docker service and the server reappeared. Then I created the disagnotics file.

nas-diagnostics-20220313-1358.zip

 

When I go back to 6.9.2 and restore my config, everything works fine with dockers enabled...

Edited by Natas
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
Reply to this topic...

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

×
Go to topic listing
×
×
  • Create New...