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.

Docker Autostart doesn't work - NetworkInterface missing

Featured Replies

Hi,

 

So for a while now I have this issue.

Whenever I start my Unraid System (sometimes you need to reboot) the Dockers can't start automatically.

So I went into edit Mode and I saw that the `Network Type` is set to none, instead of `br0`. Since this Interface is only missing for Docker (my VM templates still offers me to select it) I went to Settings/Docker and disabled the service and enabled it again.

 

I went back to edit the container and tada: network interface is already selected properly and container boots just fine.

Having a look in the Syslog prompts me:

Oct 26 09:31:42 Columbus emhttpd: Autostart enabled
Oct 26 09:31:42 Columbus root: Starting diskload
Oct 26 09:31:42 Columbus kernel: br0: port 1(eth0) entered disabled state
Oct 26 09:31:43 Columbus tips.and.tweaks: Tweaks Applied
Oct 26 09:31:43 Columbus emhttpd: Mounting disks...
Oct 26 09:31:43 Columbus emhttpd: shcmd (53): /sbin/btrfs device scan
Oct 26 09:31:43 Columbus root: Scanning for Btrfs filesystems
Oct 26 09:31:43 Columbus emhttpd: shcmd (54): mkdir -p /mnt/disk1
Oct 26 09:31:43 Columbus emhttpd: shcmd (55): mount -t xfs -o noatime,nodiratime /dev/mapper/md1 /mnt/disk1
Oct 26 09:31:43 Columbus kernel: SGI XFS with ACLs, security attributes, no debug enabled
Oct 26 09:31:43 Columbus kernel: XFS (dm-0): Mounting V5 Filesystem
Oct 26 09:31:43 Columbus dhcpcd[1735]: br0: carrier lost
Oct 26 09:31:43 Columbus avahi-daemon[5309]: Withdrawing address record for 192.168.178.26 on br0.
Oct 26 09:31:43 Columbus avahi-daemon[5309]: Leaving mDNS multicast group on interface br0.IPv4 with address 192.168.178.26.
Oct 26 09:31:43 Columbus avahi-daemon[5309]: Interface br0.IPv4 no longer relevant for mDNS.
Oct 26 09:31:43 Columbus dhcpcd[1735]: br0: deleting route to 192.168.178.0/24
Oct 26 09:31:43 Columbus dhcpcd[1735]: br0: deleting default route via 192.168.178.1

Does this means the br0 will be disabled for some time (maybe in this time also means, that the docker service is starting)?

 

What can I do to solve this issue?

 

01_nointerface.png

02_interface_after_docker_reboot.png

03_network.png

  • Author

Can I use the custom scripts to stop & start the docker Service? 

Archived

This topic is now archived and is closed to further replies.

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.