-
Notifications
You must be signed in to change notification settings - Fork 655
System broken after upgrade: /var/lib/docker contains several valid graphdrivers #2278
Comments
Please refer to this: #2194 (comment) |
So according to #2194, it should keep working if /var/lib/docker/overlay2 doesn't exist. I would expect this directory to not exist after the ros upgrade. However it does exist now:
I suppose I can recover by removing either of them, which works fine for me. Feel free to close this issue if you're not interested in fixing your upgrade path. Otherwise let me know if there's anything I can help you with. |
@niusmallnan Can you clarify which is the correct way forward? The Docker docs say that overlay2 is preferred, but my RancherOS instance has both an overlay and an overlay2 directory. overlay2 is mostly empty, except for the presence of the /l file , while 'overlay' contains all the Docker storage assets:
|
@stefanlasiewski From docker 17.06+(maybe 17.03+), Docker can automatically detect storage drivers. Maybe |
Ah I see. https://github.com/rancher/vagrant is using Docker 1.12.6. |
RancherOS Version: (ros os version)
v1.1.3 --> sudo ros os upgrade --> v1.2.0
Where are you running RancherOS? (docker-machine, AWS, GCE, baremetal, etc.)
VM (on qemu/kvm/libvirt) in a test lab (not a production system)
The user docker daemon is not running and /var/log/docker.log from point of current boot reads like this (variations of last two lines repeat a number of times):
The text was updated successfully, but these errors were encountered: