Jump to content
witalit

Docker Execution Error

8 posts in this topic Last Reply

Recommended Posts

I seem to get this issue after I shutdown unRAID. Seen some fixes for it before like re-creating docker image but it fixes it until I shutdown again. Can anyone shine some light on this?

 

Seems to be different message for some of the dockers.

 

Screenshot 2019-07-17 at 18.32.05.png

Screenshot 2019-07-17 at 18.33.28.png

unraid-diagnostics-20190717-1729.zip

Share this post


Link to post

You've got an error in the template edit the app, make change, any change, revert it and hit apply. The error will be listed in the command section

Sent from my NSA monitored device

Share this post


Link to post
Posted (edited)
1 hour ago, Squid said:

You've got an error in the template edit the app, make change, any change, revert it and hit apply. The error will be listed in the command section

Sent from my NSA monitored device
 

 

Well strangely I hav br0 set as network type but when I edit one of the dockers with this network type it does not show. I just edited one of them left network type as None and I am still unable to choose custom network, it does not appear in drop-down.

 

All of my custom network settings for my dockers have been lost, this is worse than it normally is.

Edited by witalit

Share this post


Link to post

Recently update to 6.7?  Some people have had that issue.  Just need to recreate it.

Share this post


Link to post
2 minutes ago, Squid said:

Recently update to 6.7?  Some people have had that issue.  Just need to recreate it.

 

Well I went to 6.7.1 a few weeks back. This issue has haunted me since being able to create custom networks in the GUI. Previously I was using macvlan solution in console and it worked fine. Of course I wiped out the old network and created a new one.

 

1 hour ago, Squid said:

You've got an error in the template edit the app, make change, any change, revert it and hit apply. The error will be listed in the command section

Sent from my NSA monitored device
 

I restarted docker and noticed my custom network br0 come back available to set again. Most of the dockers had their custom IP which saved me working them all out again, a couple had lost the setting. So I'm back up and running again but I suspect if I reboot now it will probably happen again. I did notice some bits in the logs but I don't completely understand what I am looking for.

 

Its more of an annoyance but I have left it for a long time I wouldn't mind resolving it. 

Share this post


Link to post
3 minutes ago, witalit said:

but I suspect if I reboot now it will probably happen again

Try it...

3 minutes ago, witalit said:

notice some bits in the logs but I don't completely understand what I am looking for

Probably call traces.  macvlans tend to be very chatty with call traces, and AFAIK nothing to worry about.

Share this post


Link to post
5 minutes ago, Squid said:

Try it...

Probably call traces.  macvlans tend to be very chatty with call traces, and AFAIK nothing to worry about.

 

Yep same issue after rebooting. I did what you said changed template, reverted and Applied to all my dockers then rebooted.

 

 

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.