Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Last started container continuously restarts network connection

Featured Replies

In my logs I'm seeing that for whichever Docker container is last started, it's continually resetting it's network adapter(?) every 60 seconds(or occasionally sooner). If I shut down all containers, and start only 1, that container will exhibit the behavior. If I start a second container, the first will stop resetting and the second container starts doing it. It does it for containers using the Network Type: Bridge and custom.

 

I want to say this coincided with the upgrade to 7.0, but I can't be sure.

https://pastebin.com/EfzLYBUH

net1.png

net2.png

docker1.png

con1.png

con2.png

unraid-diagnostics-20250119-1421.zip

Edited by Shomesomesho

docker network inspect internal 



...

 

That network may need to be deleted and fixed...

Review docker stuff here:

 

Edited by bmartino1
Data - Typo

Thanks for the reply.

I forgot to mention that I deleted the custom network and remade it with the same name. The containers threw errors when starting so I made dummy changes to each containers "network type" (change it from my custom network > bridge > back to custom network) and that allowed them to be started.

 

"Preserve user defined networks" was set to no, so I've changed that to yes. However it is still behaving the same way.

 

root@Unraid:~# docker network ls
NETWORK ID     NAME       DRIVER    SCOPE
44583c7e216b   br0        ipvlan    local
5627c3d032e2   bridge     bridge    local
0a6f1fc0c02a   host       host      local
57ecc04a16e4   internal   bridge    local
521fa5e6cf31   none       null      local
root@Unraid:~#

 

"internal" is my custom network. The name sucks. I'm not creative. Sorry.

 

I'm not sure how much of the linked thread you want me to follow.

 

Thanks again for your help.

14 hours ago, Shomesomesho said:

I'm not sure how much of the linked thread you want me to follow.

 

Disregard my thread, it has nothing to do with your issue and I have no idea why would they link to it. That being said, I've added further clarification on what I did to fix my issue in case anyone needs it in the future.

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

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.