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.

after updating to 6.3.0-rc5 Docker won't start. Reverted back to 6.2.4 same prob

Featured Replies

After updating to 6.3.0-rc5 my web ui was all messed up, couldn't browse to the flash drive. Dockers loaded but GUI said docker was disabled. Ive been using all the 6.3.0-rc's before this.

 

Hooked up monitor and everything looked fine. Went back to 6.2.4. Couldn't ping my ip but noticed my shares were on my network. Figured out the IP. got into GUI. Network settings were set to static with its normal ip but it was using a different IP. Docker wouldn't load. I tried changing the static IP and now I can't find it anywhere.

 

tower-diagnostics-20161127-1156.zip

  • Author

I think my something changed with the upgrade that is causing an issue with my reservation for the ip on my firewall which is fine. i can fix that once I get Docker up and running.

 

In included diagrams above was after docker failed to start last time so it should have everything needed. Just tried again.

 

Nov 27 09:21:28 Tower root: starting docker ...

Nov 27 09:21:28 Tower avahi-daemon[1915]: Joining mDNS multicast group on interface docker0.IPv4 with address 172.17.0.1.

Nov 27 09:21:28 Tower avahi-daemon[1915]: New relevant interface docker0.IPv4 for mDNS.

Nov 27 09:21:28 Tower avahi-daemon[1915]: Registering new address record for 172.17.0.1 on docker0.IPv4.

Nov 27 09:21:28 Tower avahi-daemon[1915]: Withdrawing address record for 172.17.0.1 on docker0.

Nov 27 09:21:28 Tower avahi-daemon[1915]: Leaving mDNS multicast group on interface docker0.IPv4 with address 172.17.0.1.

Nov 27 09:21:28 Tower avahi-daemon[1915]: Interface docker0.IPv4 no longer relevant for mDNS.

Nov 27 09:21:28 Tower avahi-daemon[1915]: Joining mDNS multicast group on interface docker0.IPv4 with address 172.17.0.1.

Nov 27 09:21:28 Tower avahi-daemon[1915]: New relevant interface docker0.IPv4 for mDNS.

Nov 27 09:21:28 Tower avahi-daemon[1915]: Registering new address record for 172.17.0.1 on docker0.IPv4.

Nov 27 09:21:28 Tower avahi-daemon[1915]: Withdrawing address record for 172.17.0.1 on docker0.

Nov 27 09:21:28 Tower avahi-daemon[1915]: Leaving mDNS multicast group on interface docker0.IPv4 with address 172.17.0.1.

Nov 27 09:21:28 Tower avahi-daemon[1915]: Interface docker0.IPv4 no longer relevant for mDNS.

Nov 27 09:21:38 Tower emhttp: shcmd (392): umount /var/lib/docker |& logger

Nov 27 09:21:51 Tower emhttp: shcmd (419): set -o pipefail ; /usr/local/sbin/mount_image '/mnt/cache/docket.img' /var/lib/docker 30 |& logger

Nov 27 09:21:51 Tower kernel: BTRFS info (device loop0): disk space caching is enabled

Nov 27 09:21:51 Tower kernel: BTRFS: has skinny extents

Nov 27 09:21:51 Tower root: Resize '/var/lib/docker' of 'max'

Nov 27 09:21:51 Tower emhttp: shcmd (420): /etc/rc.d/rc.docker start |& logger

Nov 27 09:21:51 Tower kernel: BTRFS info (device loop0): new size for /dev/loop0 is 32212254720

Nov 27 09:21:51 Tower root: starting docker ...

Nov 27 09:21:51 Tower avahi-daemon[1915]: Joining mDNS multicast group on interface docker0.IPv4 with address 172.17.0.1.

Nov 27 09:21:51 Tower avahi-daemon[1915]: New relevant interface docker0.IPv4 for mDNS.

Nov 27 09:21:51 Tower avahi-daemon[1915]: Registering new address record for 172.17.0.1 on docker0.IPv4.

Nov 27 09:21:51 Tower avahi-daemon[1915]: Withdrawing address record for 172.17.0.1 on docker0.

Nov 27 09:21:51 Tower avahi-daemon[1915]: Leaving mDNS multicast group on interface docker0.IPv4 with address 172.17.0.1.

Nov 27 09:21:51 Tower avahi-daemon[1915]: Interface docker0.IPv4 no longer relevant for mDNS.

Nov 27 09:21:51 Tower avahi-daemon[1915]: Joining mDNS multicast group on interface docker0.IPv4 with address 172.17.0.1.

Nov 27 09:21:51 Tower avahi-daemon[1915]: New relevant interface docker0.IPv4 for mDNS.

Nov 27 09:21:51 Tower avahi-daemon[1915]: Registering new address record for 172.17.0.1 on docker0.IPv4.

Nov 27 09:21:51 Tower avahi-daemon[1915]: Withdrawing address record for 172.17.0.1 on docker0.

Nov 27 09:21:51 Tower avahi-daemon[1915]: Leaving mDNS multicast group on interface docker0.IPv4 with address 172.17.0.1.

Nov 27 09:21:51 Tower avahi-daemon[1915]: Interface docker0.IPv4 no longer relevant for mDNS.

Nov 27 09:22:01 Tower emhttp: shcmd (422): umount /var/lib/docker |& logger

Nov 27 09:22:01 Tower crond[1715]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &>/dev/null

Nov 27 09:23:01 Tower crond[1715]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &>/dev/null

 

  • Author

fix common problems is reporting that flash is read only.

 

"Drive mounted read-only or completely full. Begin Investigation Here:  Note: failing this test will also mean that you will be unable to perform a clean shutdown of your server"

  • Author

ok figured out its dhcp in safe mode...

 

ok booting into regular mode after removing all plugins and extra things. Flash/boot drive works again. I can browse to the share.

 

I still can't docker to start. I deleted the docker image and tried. It created the image but won't start.

 

Latest Diag.

tower-diagnostics-20161127-1337.zip

  • Author

installed the latest prerelease again and it seems like docker is starting again.

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.