docker pull fail with failed to register layer: Error processing tar file(exit status 1): invalid argument #97
Comments
linarnan
changed the title
|
same as this issue just close this. |
|
after given |
|
build cmd: |
|
I have the same pillarlei@DESKTOP-V3N3P9H:~$ sudo docker pull redis pillarlei@DESKTOP-V3N3P9H:~$ docker info WARNING: No memory limit support how can I deal with it. |
|
another same post here: moby/moby#34817 , |
|
I have same issue. However, I am in chroot environment. Wondering if it's possible to make docker work in such environment. ./docker infoDEBU[2019-05-27T14:15:14.212268660Z] Calling GET /_ping WARNING: No cpu cfs quota support ./docker run hello-worldDEBU[2019-05-27T13:59:01.403488020Z] Calling GET /_ping |
|
I solved this problem reading this info: https://docs.docker.com/engine/security/rootless/#docker-pull-errors I figured it out reading this link: https://docs.oracle.com/cd/E37670_01/E75728/html/ol-docker-userns-remap.html And increasing those value contained in those files (/etc/subuid and /etc/subgid) and reboot (not mentioned) as this link recommended: https://ubuntu.com/blog/custom-user-mappings-in-lxd-containers The only thing that I noticed is that my path to the storage disk was renamed from "DATA" to "DATA1" and I don't know why this happened. DATA is innaccesible from terminal with the typical "permission denied" message and from GUI file browser it appeared as always "DATA". But hey, I finally was able to pull the image that I wanted and I can continue with my life happily ever after. :D! UPDATE: I had to change back those values for /etc/subuid and /etc/subgid since my storage disk (ntfs filesystem) was changing names every time I rebooted. It looks like that strange behavior is because ntfs is not supported to do this kind of things, a solution was change back default parameter in /etc/docker/daemon.json file, run docker pull "image", then move all folders from /var/lib/docker/ to the new location (ntfs disk) following these instructions https://www.guguweb.com/2019/02/07/how-to-move-docker-data-directory-to-another-location-on-ubuntu/ I had to move it to another location because my ssd is very small and those images are quite big to be stored in my ssd. I hope this could help you guys. |
|
@mike-bioinfo try this one, https://pdiway.com/articles/how-to-move-docker-data-directory/, it solved my issue with ntfs. |
Behavior
I'm building vm image for openstack, I wanna pull some docker images during build image process.
some how it can't start docker daemon during package installation.
so i just start daemon manually
here is my script:
looks like pull image correctly, but have some problem while register layer
Steps to reproduce the behavior
Output of
docker version:Output of
docker info:Additional environment details (AWS, VirtualBox, physical, etc.)
vm disk image building process (use https://docs.openstack.org/diskimage-builder/latest/index.html)
The text was updated successfully, but these errors were encountered: