Issues running Docker engine after rolling back to 6.2.4

[emmcee]

I had Kernel Panics after updating to 6.3.2 (see this thread), so I tried downgrading back to 6.2.4. The system is stable on 6.2.4, but Docker refuses to run. When I set it to "Enabled" my GUI slows to a crawl, disable it and the GUI is back to normal.

 

I've taken a virgin 6.2.4 image and just added the cfgs and still have the same issue. I've also deleted my docker image.

 

I've attached the diagnostics, but the highlights are below.

 

Thanks in advance for any help.

 

docker.log:

 

time="2017-02-23T11:03:15.018972628-08:00" level=fatal msg="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"

 

system.log:

 

b 23 11:22:25 Tower emhttp: shcmd (560): set -o pipefail ; /usr/local/sbin/mount_image '/mnt/user/system/docker/docker.img' /var/lib/docker 20 |& logger
Feb 23 11:22:25 Tower kernel: BTRFS info (device loop0): disk space caching is enabled
Feb 23 11:22:25 Tower kernel: BTRFS: has skinny extents
Feb 23 11:22:25 Tower kernel: BTRFS info (device loop0): new size for /dev/loop0 is 21474836480
Feb 23 11:22:25 Tower root: Resize '/var/lib/docker' of 'max'
Feb 23 11:22:25 Tower emhttp: shcmd (562): /etc/rc.d/rc.docker start |& logger
Feb 23 11:22:25 Tower root: starting docker ...
Feb 23 11:22:25 Tower avahi-daemon[2323]: Joining mDNS multicast group on interface docker0.IPv4 with address 172.17.0.1.
Feb 23 11:22:25 Tower avahi-daemon[2323]: New relevant interface docker0.IPv4 for mDNS.
Feb 23 11:22:25 Tower avahi-daemon[2323]: Registering new address record for 172.17.0.1 on docker0.IPv4.
Feb 23 11:22:25 Tower avahi-daemon[2323]: Withdrawing address record for 172.17.0.1 on docker0.
Feb 23 11:22:25 Tower avahi-daemon[2323]: Leaving mDNS multicast group on interface docker0.IPv4 with address 172.17.0.1.
Feb 23 11:22:25 Tower avahi-daemon[2323]: Interface docker0.IPv4 no longer relevant for mDNS.
Feb 23 11:22:25 Tower emhttp: shcmd (564): umount /var/lib/docker |& logger

 

 

Edited February 23, 2017 by emmcee

[RobJ]

3 hours ago, emmcee said:

I had Kernel Panics after updating to 6.3.2 (see this thread), so I tried downgrading back to 6.2.4. The system is stable on 6.2.4, but Docker refuses to run. When I set it to "Enabled" my GUI slows to a crawl, disable it and the GUI is back to normal.

It's my understanding that rolling back from 6.3 to 6.2 requires redoing the Docker setup.  Just disable and delete docker.img, then enable, recreate, and re-add your templates back.

[emmcee]

I tried that, but Docker still doesn't run. The same entries as above appear in the syslog when I try. 

[RobJ]

I apologize, I didn't take a close look at your logs above.  That's clearly a different issue, one I haven't seen before, and I have no ideas yet.

[emmcee]

Thanks anyway Rob. I created a virgin 6.2.4 flash this morning and added the bare minimum configs needed. Docker is now running and I'm rebuilding my containers.

[emmcee]

So I had this problem again. It seems that something happens to the docker image when you update to 6.3.2 which causes problems when you downgrade.

 

The solution was

 

- disable Docker

- delete the docker image

- reboot

- re-enable docker

- recreate your dockers from the templates

 

and you should be back in the game

 

Hope this helps someone.