December 31, 20196 yr I have one docker container that will not start after a reboot. Every time, I have to go into the container, edit it, change something (anything) and hit Apply, then it starts and runs just fine. It is the only container I have that does that, and I'm struggling to understand why. It isn't the end of the world, since a simple edit/apply fixes it until next reboot, but it is just weird. The container in question is named "avahi". As you may guess, it runs the avahi mDNS reflector service. unraid-diagnostics-20191231-1720.zip
December 31, 20196 yr Dec 31 16:23:46 UNRAID rc.docker: avahi: Error response from daemon: network 5716ed749b300cf862484f2d18f6c465268b989b997f4dcc8af9d56a4f72ad30 not found The network that it's looking for isn't available yet at boot.... Where is that network it's using being created?
December 31, 20196 yr Author I thought it might be that.... If I remember correctly I created it on the console of the unraid server, than I added this to my container as a post argument: "; docker network connect --ip 192.168.2.252 br3 avahi" I need the docker to talk to 2 networks (the whole point of the mDNS reflector), and couldn't figure out any other way to bind the container to 2 networks.
December 31, 20196 yr Give it more of a delay before startup? I don't use custom networks, so can't offer much else in assistance though...
December 31, 20196 yr Author 1 minute ago, Squid said: Give it more of a delay before startup? I actually forgot that was adjustable. 😫 I put the container last to buy more time, but I haven't tried increasing the delay. Duh... I'll try that next.
December 31, 20196 yr Community Expert 3 minutes ago, JasonJoel said: put the container last to buy more time, but I haven't tried increasing the delay. Duh... I'll try that next. Remember that when adding a delay it needs to be added to the previous container as the delay is the length of time to wait after starting a container before attempting to start the next one.
January 1, 20206 yr Author 20 minutes ago, itimpi said: Remember that when adding a delay it needs to be added to the previous container as the delay is the length of time to wait after starting a container before attempting to start the next one. I did remember that but thank you for the reminder as that isn't very intuitive/obvious!
Archived
This topic is now archived and is closed to further replies.