No old docker images will be displayed after upgrade

[holm74]

Hi there,

I recently updated app-emulation/docker to 18.09.2.

But typing docker images all my images will not be displayed anymore.


They are still on my hardddisc (under /var/lib/docker/volumes) but as I checked it they will now be stored under /var/lib/docker/overlay2 .


Just to mention: the docker environment is working. I pulled for example wordpress with docker pull wordpress. Afterwards using docker images the image of wordpress will be displayed (and can be used)

So the question is: can I somehow "convert" my old docker image environment to the current one (18.09.02) in a clean way?

Any links, news, whatever?


Thanks for any help,


Holm

[r7l]

There are different drivers for your images. I am using overlay2 anyways. Did you use anything else prior to that update?

[holm74]

I did not change anything on the flags: before and after the upgrade I used:


USE="container-init overlay seccomp -apparmor -aufs -btrfs -device-mapper -hardened -pkcs11"

So I think this should not be the reason. Haven't read something about that.

Thanks for any hints,

Holm

[r7l]

Reading your post again, i wonder if you mix up the 2 things. Images are kinda static blobs that come from an outside source while volumes are like local discs that contain your data. If you want to swap out all the images you had, you can simply delete all the images you have on your docker and pull them back in again. Volumes on the other hand should be checked for any important data prior of deleting them.

[holm74]

I think that is the second best choice: when I pull all the images I am pretty sure all the volumes will not work anymore.

So I think it is better to first try to fix it (never happened before - after all upgrades I still could use my images and boot my volumes without pull them all again) and keep the second choice (pull all again) in mind (because there are a lot of self build images which costs me a lot of time)


Maybe there is a choice to restore the images so I can still use them.

[jroth]

I also just lost all my docker images in the docker update (but interestingly, it only happened on one of my two Gentoo machines, both of which I updated docker on...). I'd also like to know how to get them back - there's a custom image I'd configured that I don't want to lose the work on.

[sgroth]

I lost my images and containers and got them back.

I ran a few find commands in /var/lib/docker and discovered that the devicemapper subtree of /var/lib/docker files like these:

Code: Select all

image/devicemapper/layerdb/sha256/cd7100a72410606589a54b932cabd804a17f9ae5b42a1882bd56d263e02b6215
image/devicemapper/layerdb/sha256/cd7100a72410606589a54b932cabd804a17f9ae5b42a1882bd56d263e02b6215/cache-id
image/devicemapper/layerdb/sha256/cd7100a72410606589a54b932cabd804a17f9ae5b42a1882bd56d263e02b6215/diff
image/devicemapper/layerdb/sha256/cd7100a72410606589a54b932cabd804a17f9ae5b42a1882bd56d263e02b6215/size
image/devicemapper/layerdb/sha256/cd7100a72410606589a54b932cabd804a17f9ae5b42a1882bd56d263e02b6215/tar-split.json.gz
image/devicemapper/layerdb/sha256/e8624bf9b6a3d284c2b94ee4355d2a0bc339d2aa9ba4bb5dfbaaa5a80f1a7b85
image/devicemapper/layerdb/sha256/e8624bf9b6a3d284c2b94ee4355d2a0bc339d2aa9ba4bb5dfbaaa5a80f1a7b85/cache-id
image/devicemapper/layerdb/sha256/e8624bf9b6a3d284c2b94ee4355d2a0bc339d2aa9ba4bb5dfbaaa5a80f1a7b85/diff
image/devicemapper/layerdb/sha256/e8624bf9b6a3d284c2b94ee4355d2a0bc339d2aa9ba4bb5dfbaaa5a80f1a7b85/parent
image/devicemapper/layerdb/sha256/e8624bf9b6a3d284c2b94ee4355d2a0bc339d2aa9ba4bb5dfbaaa5a80f1a7b85/size
image/devicemapper/layerdb/sha256/e8624bf9b6a3d284c2b94ee4355d2a0bc339d2aa9ba4bb5dfbaaa5a80f1a7b85/tar-split.json.gz

I tried adding the device-mapper USE flag and after rebuild and daemon restart the images and containers reappeared.