Closed Root-voidX closed 2 years ago
hi can you tell me which linux distro you are using? I have tested this successfully in my desktop ubuntu22.04
docker save centos:7 -o centos7.tar
mkdir somedir
mv centos7.tar somedir/
udocker load -i somedir/centos7.tar
udocker images
REPOSITORY
centos:7
We found a similar issue for CentOS and Rockylinux based tarballs which contain some layers referenced as symlinks. I think this behaviour may have arisen with newer versions of docker (maybe buildkit?) or udocker, since we did not have it in the past.
udocker verify
points to the problem layers which can be seen in the tarball to be the symlink layers
Two workarounds
docker save ${NAME} | udocker load -
(but only works in env where docker is installed...)Somewhat related discussion about this behaviour appearing: https://forums.docker.com/t/docker-save-images-image-tarball-has-symlinks-between-layers/52022/2
EDIT: I realised our issue is at the udocker create
not udocker load
step, so probably not relevant to this issue. Will open a new issue if can find steps to reproduce with an image from dockerhub.
EDIT2: When playing around with udocker load
, I noticed that there is a difference between
udocker load -i somefile.tar # fails
udocker load -i ./somefile.tar # works
When I try to use udocker load -i I get this error: