Jump to content
Sign in to follow this  
JasonJoel

Docker container won't start after reboot until edited

7 posts in this topic Last Reply

Recommended Posts

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

Share this post


Link to post
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?

Share this post


Link to post

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.

Share this post


Link to post

Give it more of a delay before startup?  I don't use custom networks, so can't offer much else in assistance though...

Share this post


Link to post
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.

Share this post


Link to post
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.

Share this post


Link to post
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!

Share this post


Link to post

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.

Sign in to follow this