I downgraded, installed the ZFS plugin, and replaced my cache partition with a ZFS pool. I moved all my data, which I backed up to the array, back to the new ZFS partition at /mnt/zfs.

 

Then I realized I should remake my Docker image, since it would be too new for the current version of Docker in this release.

 

It won't start, though:

 

Dec 3 20:38:37 Tower root: starting docker ...
Dec 3 20:38:37 Tower avahi-daemon[4866]: Joining mDNS multicast group on interface docker0.IPv4 with address 172.17.0.1.
Dec 3 20:38:37 Tower avahi-daemon[4866]: New relevant interface docker0.IPv4 for mDNS.
Dec 3 20:38:37 Tower avahi-daemon[4866]: Registering new address record for 172.17.0.1 on docker0.IPv4.
Dec 3 20:38:37 Tower avahi-daemon[4866]: Withdrawing address record for 172.17.0.1 on docker0.
Dec 3 20:38:37 Tower avahi-daemon[4866]: Leaving mDNS multicast group on interface docker0.IPv4 with address 172.17.0.1.
Dec 3 20:38:37 Tower avahi-daemon[4866]: Interface docker0.IPv4 no longer relevant for mDNS.
Dec 3 20:38:37 Tower emhttp: shcmd (1723): umount /var/lib/docker |& logger
Dec 3 20:39:01 Tower emhttp: shcmd (1735): set -o pipefail ; /usr/local/sbin/mount_image '/mnt/zfs/system/docker/docker.img' /var/lib/docker 20 |& logger
Dec 3 20:39:01 Tower kernel: BTRFS info (device loop0): disk space caching is enabled
Dec 3 20:39:01 Tower kernel: BTRFS: has skinny extents
Dec 3 20:39:01 Tower root: Resize '/var/lib/docker' of 'max'
Dec 3 20:39:01 Tower emhttp: shcmd (1736): /etc/rc.d/rc.docker start |& logger
Dec 3 20:39:01 Tower kernel: BTRFS info (device loop0): new size for /dev/loop0 is 21474836480
Dec 3 20:39:01 Tower root: starting docker ...
Dec 3 20:39:01 Tower avahi-daemon[4866]: Joining mDNS multicast group on interface docker0.IPv4 with address 172.17.0.1.
Dec 3 20:39:01 Tower avahi-daemon[4866]: New relevant interface docker0.IPv4 for mDNS.
Dec 3 20:39:01 Tower avahi-daemon[4866]: Registering new address record for 172.17.0.1 on docker0.IPv4.
Dec 3 20:39:01 Tower avahi-daemon[4866]: Withdrawing address record for 172.17.0.1 on docker0.
Dec 3 20:39:01 Tower avahi-daemon[4866]: Leaving mDNS multicast group on interface docker0.IPv4 with address 172.17.0.1.
Dec 3 20:39:01 Tower avahi-daemon[4866]: Interface docker0.IPv4 no longer relevant for mDNS.
Dec 3 20:39:02 Tower emhttp: shcmd (1738): umount /var/lib/docker |& logger

 

It just stops instantly. Attempting to start docker daemon manually:

 

INFO[0000] [graphdriver] using prior storage driver "btrfs" 
INFO[0000] Graph migration to content-addressability took 0.00 seconds 
INFO[0000] Firewalld running: false                     
INFO[0000] Default bridge (docker0) is assigned with an IP address 172.17.0.0/16. Daemon option --bip can be used to set a preferred IP address 
FATA[0000] Error starting daemon: Error initializing network controller: Error creating default "bridge" network: Failed to setup IP tables, cannot acquire Interface address: Interface docker0 has no IPv4 addresses

 

Attaching diagnostics.

 

E: New symptom. Bridged networking isn't working for VMs, either. E2: Needed to reboot the VM.

tower-diagnostics-20161203-2039.zip

There might be changes in the network settings that is causing this. You could try to delete network.cfg and network-rules.cfg and reboot and set up your network again.

Just a stupid question before you do that. You have enabled bridge in the network settings or checked if its enabled?

Thanks for that tip. And I notice that network.cfg has not been recreated, and network-rules.cfg never existed. Did it matter that there was a bond named "bond0" and no named bridge in the old configuration?

Thanks for that tip. And I notice that network.cfg has not been recreated, and network-rules.cfg never existed. Did it matter that there was a bond named "bond007" and no named bridge in the old configuration?

It probably mattered.

You need to set  up the network again for the configuration to be saved I think.

I never set it up in the first place, since it was just the auto detected defaults with DHCP everything.