I keep getting EOF error when trying to pull images:
docker pull dpage/pgadmin4
Pull complete
942bbf3d7389: Downloading 1.82kB/1.82kB
fbe23c71dc3b: Download complete
7c1be9e99602: Download complete
ccc31a15f27f: Download complete
617b6e01309f: Download complete
e6cfa0ba7132: Download complete
9dd539b143fa: Downloading 3.15kB/3.15kB
6f3ff58d53db: Download complete
a79e40a556fb: Download complete
b05884a10df3: Download complete
3a39531f7518: Download complete
0337d3baf297: Downloading 9.88kB/9.88kB
c7a9de9c5d61: Download complete
unexpected EOF
I've tried to change the network and use my mobile hotspot. Sometimes it works and sometimes it does not.
Related
Attempting to pull a docker image and got the following result:
2f94e549220a: Pull complete
72007112f52f: Pull complete
e1886834052f: Pull complete
934c6c525c1d: Pull complete
6bc1674f1e8f: Pull complete
07e666cf45ea: Pull complete
609b62e99828: Extracting 5.23GB/5.23GB
bbd38441b44b: Download complete
4e6cf32e909d: Download complete
3ed8401905bf: Download complete
failed to register layer: sync /var/lib/docker/image/overlay2/layerdb/tmp/write-set-315662188/diff: input/output error
Judging by the input/output error, and knowing that I had less than ~10GB left on my drive, I cleaned up some more space and reran the pull command. Error was resolved.
I am following this tutorial on using python packages with Serverless. Everything was working until I went to deploy with serverless-deploy. Then I got the below error. Does anyone know how to remedy this?
Other info:
OS: Windows 10
WLS Distro: Ubuntu v2
Serverless: Generated requirements from C:\Users\path-to-project\numpy-test\requirements.txt in C:\Users\path-to-project\numpy-test\.serverless\requirements.txt...
Serverless: Installing requirements from C:\Users\myname\AppData\Local\UnitedIncome\serverless-python-requirements\Cache\e1e710a0b480eb4e7e39fca7f1ff66fff4b6f5d572ded1d71d5082f9afe1de06_slspyc\requirements.txt ...
Serverless: Docker Image: lambci/lambda:build-python3.6
Serverless: Using download cache directory C:\Users\myname\AppData\Local\UnitedIncome\serverless-python-requirements\Cache\downloadCacheslspyc
Serverless: Running docker run --rm -v C\:/Users/myname/AppData/Local/UnitedIncome/serverless-python-requirements/Cache/e1e710a0b480eb4e7e39fca7f1ff66fff4b6f5d572ded1d71d5082f9afe1de06_slspyc\:/var/task\:z -v C\:/Users/myname/AppData/Local/UnitedIncome/serverless-python-requirements/Cache/downloadCacheslspyc\:/var/useDownloadCache\:z -u 0 lambci/lambda\:build-python3.6 python -m pip install -t /var/task/ -r /var/task/requirements.txt --cache-dir /var/useDownloadCache...
Error ---------------------------------------------------
Error: STDOUT:
STDERR: Unable to find image 'lambci/lambda:build-python3.6' locally
build-python3.6: Pulling from lambci/lambda
832a9fa6947e: Pulling fs layer
fe6bfd165af8: Pulling fs layer
c61e272c0488: Pulling fs layer
7022c87fa044: Pulling fs layer
ab51495a619c: Pulling fs layer
28e9e78ca9d3: Pulling fs layer
6b8ec334143c: Pulling fs layer
7022c87fa044: Waiting
6b8ec334143c: Waiting
ab51495a619c: Waiting
28e9e78ca9d3: Waiting
c61e272c0488: Verifying Checksum
c61e272c0488: Download complete
7022c87fa044: Verifying Checksum
7022c87fa044: Download complete
ab51495a619c: Verifying Checksum
ab51495a619c: Download complete
28e9e78ca9d3: Download complete
6b8ec334143c: Download complete
832a9fa6947e: Verifying Checksum
832a9fa6947e: Download complete
fe6bfd165af8: Download complete
832a9fa6947e: Pull complete
fe6bfd165af8: Pull complete
c61e272c0488: Pull complete
7022c87fa044: Pull complete
ab51495a619c: Pull complete
28e9e78ca9d3: Pull complete
6b8ec334143c: Pull complete
Digest: sha256:9b1cea555bfed62d1fc9e9130efa9842ee144ef02e2a6a266f1c9e6adeb0866f
Status: Downloaded newer image for lambci/lambda:build-python3.6
ERROR: Could not find a version that satisfies the requirement numpy==1.21.2
ERROR: No matching distribution found for numpy==1.21.2
WARNING: You are using pip version 21.0; however, version 21.2.4 is available.
You should consider upgrading via the '/var/lang/bin/python -m pip install --upgrade pip' command.
From Pypi, numpy==1.21.2 requires at python version to be Python >=3.7, <3.11.
You should either upgrade your lambda image to lambci/lambda:build-python3.8 or downgrade the version of numpy to numpy==1.19.5 which supports python3.6.
This error appears when I try to press ANY docker image.
This is a Fresh installation of docker in 5.0.21-rt14-MANJARO
Unable to find image 'ubuntu:16.04' locally
16.04: Pulling from library/ubuntu
35b42117c431: Extracting [==================================================>] 43.84MB/43.84MB
ad9c569a8d98: Download complete
293b44f45162: Download complete
0c175077525d: Download complete
docker: failed to register layer: Error processing tar file(exit status 1): Error cleaning up after pivot: remove /.pivot_root336598748: device or resource busy.
See 'docker run --help'.
I had the same error with the 5.0.xxx Kernel. Switching back to 4.19.59-1-MANJARO solved the problem...
EDIT:
you might try:
sudo tee /etc/modules-load.d/loop.conf <<< "loop"
sudo modprobe loop
then reboot and try again.
I'm now on 5.2.4-1-MANJARO
and everything works.
I followed these instructions here:
https://linuxhint.com/docker_arch_linux/
Yes, the problem is with your kernel version. I installed the version 5.2.4 and works very well.
Version with problem: 5.0.21
My docker develop site and private registry located on site A. The production site B is connecting by 1 MB bandwidth network.
I have build a large image about 14GB and put it on private docker registry:2.
Because transfer 14GB by 'docker pull' always hang for small network bandwidth. I use docker save then compressed as xz file and transfer to production site. The tar.xz file is about 800MB and suitable for first setup on production site.
Now, I just append one line RUN script on Dockerfile to change the image and push to registry in 1 second. I wish it could pull the samll change on production site for only a few seconds. But, The docker pull command always trying to pull an old large layer about 1.4 GB.
I'm wonder why it is not cached by the first time 'docker load'? Is there any method to improve pull speed.
$ docker pull 192.168.1.2:5000/large
Using default tag: latest
latest: Pulling from large
cbddbc0189a0: Already exists
d79d36371fdd: Already exists
22a28ad6d786: Already exists
8d977d3c35c4: Already exists
82bf6088772f: Already exists
c3721275c963: Already exists
e6094577f1ab: Already exists
fae943dde872: Already exists
a750c973438c: Already exists
eaa46ee01cde: Already exists
c6a587da73bc: Downloading [> ] 1.596MB/1.393GB
1a237f393bcc: Download complete
2f9ea1299990: Download complete
084da7095dce: Download complete
56dc8872f673: Download complete
b564807882b8: Download complete
c6763845a161: Download complete
ab30373e73e1: Download complete
d215b08dc34e: Download complete
b4969cff1817: Download complete
56d6d67ceed8: Downloading [===> ] 463.2kB/7.016MB
eec215ecbaa9: Download complete
5bd3119d46dd: Download complete
dde99cd229a7: Download complete
a9625b7300e1: Download complete
b9bb74922ed7: Download complete
23d0d72df613: Download complete
85bf8e03320b: Download complete
00120183b69f: Download complete
Locally, I just ran docker pull wordpress:
$docker pull wordpress
Using default tag: latest
latest: Pulling from library/wordpress
7268d8f794c4: Already exists
a3ed95caeb02: Download complete
38331772e700: Pull complete
74507bbf90f9: Downloading [=========> ] 13.47 MB/69.26 MB
c6734ca38ed8: Download complete
616f76e75b9d: Download complete
763f79680cbb: Download complete
e70b2d142af2: Download complete
62012af41161: Download complete
33a120b6dfa1: Download complete
ea474957253d: Download complete
757eabb832b4: Downloading [=============> ] 8.518 MB/31.61 MB
286426d94368: Download complete
cde52c0a5f98: Download complete
7c925ca09be1: Download complete
7c4e1930593c: Downloading [============> ] 1.127 MB/4.443 MB
9c4eeb87aed8: Waiting
e13c8ae5c7d1: Waiting
730edfa5d07f: Waiting
The Using default tag: latest is self-explanatory. But, it's not clear to me what all of those hashes, e.g. c6734ca38ed8 and a3ed95caeb02, represent.
Could you please explain?
Those are sha256 hashes for all layers depends on Docker image.
Docker images are based on "layers", just like aufs or overlayFS.
So, when you pull something, Docker need all deps for some image which in a nutshell are just a differences between "commits".
You can inspect all deps using docker images -a to print all layers available. Or use something like this
Layers for docker pull mongo as example.