centos docker:Error while pulling image - docker

I'm installing docker on CentOS 7 and i have this issue :
$ proxychains4 docker run hello-world
[proxychains] config file found: /usr/local/etc/proxychains.conf
[proxychains] preloading /usr/local/lib/libproxychains4.so
[proxychains] DLL init: proxychains-ng 4.12
Unable to find image 'hello-world:latest' locally
Pulling repository docker.io/library/hello-world
docker: Error while pulling image: Get https://index.docker.io/v1/repositories/library/hello-world/images: tls: oversized record received with length 26992.
the docker message :
Client:
Version: 1.12.6
API version: 1.24
Go version: go1.6.4
Git commit: 78d1802
Built: Tue Jan 10 20:20:01 2017
OS/Arch: linux/amd64
Server:
Version: 1.12.6
API version: 1.24
Go version: go1.6.4
Git commit: 78d1802
Built: Tue Jan 10 20:20:01 2017
OS/Arch: linux/amd64
the centos message:
Linux localhost.localdomain 3.10.0-514.21.2.el7.x86_64 #1 SMP Tue Jun 20 12:24:47 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
Can anyone help me to find a solution for this issue? Thank you.

Related

Un-responsive docker containers

I see that docker containers in my host show as Running/Up , however when I try to exec , I see .
rpc error: code = 2 desc = containerd: container not found
I don't see any related processes running on ps -aef output.
Looking through the dockerd logs I see -
level=error msg="containerd: get exit status" error="containerd:
process has not exited" id=e4e5d58359 pid=bba1944c4 systemPid=5132
docker version:
Client: Version: 1.13.1 API version: 1.26 Go
version: go1.7.5 Git commit: 092cba3 Built: Wed Feb 8
06:50:14 2017 OS/Arch: linux/amd64
Server: Version: 1.13.1 API version: 1.26 (minimum version
1.12) Go version: go1.7.5 Git commit: 092cba3 Built: Wed Feb 8 06:50:14 2017 OS/Arch: linux/amd64 Experimental: false
What might be causing this behavior ? Pointers?
This issue is fixed since v17.12.
Version 18.03 is the latest supported release so you should do upgrade your docker to latest edition.

Tag 1.10.3 AS base not found in repository docker.io/library/golang

when i try to compile moby (the latest version 2018.08.07), the outcome like this:
docker build -t "docker-dev:master" -f "Dockerfile" .
Sending build context to Docker daemon 43.28 MB
Step 1 : FROM golang:1.10.3 AS base
Pulling repository docker.io/library/golang
Tag 1.10.3 AS base not found in repository docker.io/library/golang
make: *** [build] Error 1
my host machine is : centos 6
Linux li1202-249.members.linode.com 4.15.13-x86_64-linode106 #1 SMP Tue Mar 27 14:42:14 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
my docker version is:
[root#li1202-249 ~]# docker version
Client:
Version: 1.9.1
API version: 1.21
Go version: go1.4.3
Git commit: a34a1d5
Built: Fri Nov 20 17:56:04 UTC 2015
OS/Arch: linux/amd64
Server:
Version: 1.9.1
API version: 1.21
Go version: go1.4.3
Git commit: a34a1d5
Built: Fri Nov 20 17:56:04 UTC 2015
OS/Arch: linux/amd64
what's the wrong configuration i had set?
Multi-stage builds are a new feature requiring Docker 17.05 or higher on the daemon and client.
https://docs.docker.com/develop/develop-images/multistage-build/
Your (ancient) Docker version doesn't support multi-stage builds. You can update Docker, build everything in one stage, or use the builder pattern described in the article linked above.

"docker pull redis" fails on Docker for Windows

I've installed Docker EE for Windows Server 2016 and was able to pull and run the hello-world example.
When I invoke "docker pull redis" , I get:
Using default tag: latest
latest: Pulling from library/redis
no matching manifest for windows/amd64 in the manifest list entries
My docker versions:
Client:
Version: 17.10.0-ee-preview-2
API version: 1.32
Go version: go1.8.3
Git commit: 10e292d
Built: Thu Sep 21 19:58:53 2017
OS/Arch: windows/amd64
Server:
Version: 17.10.0-ee-preview-2
API version: 1.32 (minimum version 1.24)
Go version: go1.8.3
Git commit: 777d4a1
Built: Thu Sep 21 20:08:05 2017
OS/Arch: windows/amd64
Experimental: false
Not sure what I'm doing wrong here.
As the docker info shows, the server is not started in experiemental mode.
You need to start docker server with experiemental mode on windows server. Check linux-containers-on-windows to see how you can do that.

Docker - Inbound network access to host stops when new network is created

Anytime I create a new docker network on the host, I loose inbound network access. If I have an active SSH session it boots me off. The only way to restore it is to delete the network.
[admin#server1 ~]$ docker version
Client:
Version: 17.06.0-ce
API version: 1.30
Go version: go1.8.3
Git commit: 02c1d87
Built: Fri Jun 23 21:20:36 2017
OS/Arch: linux/amd64
Server:
Version: 17.06.0-ce
API version: 1.30 (minimum version 1.12)
Go version: go1.8.3
Git commit: 02c1d87
Built: Fri Jun 23 21:21:56 2017
OS/Arch: linux/amd64
Experimental: false
[admin#server1 ~]$ uname -a
Linux server1 3.10.0-514.26.2.el7.x86_64 #1 SMP Tue Jul 4 15:04:05 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
[admin#server1 ~]$ cat /etc/centos-release
CentOS Linux release 7.3.1611 (Core)
Upgraded to latest version as Tarun suggested and it fixed the issue.
[root#server1 ~]# docker --version
Docker version 17.06.2-ce, build cec0b72

Docker unsupported manifest mediatype

Error when running docker pull/run on many image types. Here is just one example.
docker run --rm -it -p 4040:4040 gettyimages/spark bin/run-example SparkPi 10
ERRO[63011] Handler for POST /v1.22/containers/create returned error: No such image: gettyimages/spark:latest
Unable to find image 'gettyimages/spark:latest' locally
ERRO[63011] Handler for POST /v1.22/images/create returned error: unsupported manifest mediatype: application/vnd.docker.distribution.manifest.v1+prettyjws
docker: Error response from daemon: unsupported manifest mediatype: application/vnd.docker.distribution.manifest.v1+prettyjws.
docker version
Client:
Version: 1.10.0-rc1
API version: 1.22
Go version: go1.5.3
Git commit: 677c593
Built: Fri Jan 15 18:17:17 2016
OS/Arch: linux/amd64
Server:
Version: 1.10.0-rc1
API version: 1.22
Go version: go1.5.3
Git commit: 677c593
Built: Fri Jan 15 18:17:17 2016
OS/Arch: linux/amd64
You need to update docker; you're running a release candidate of docker 1.10.0. Update to the latest release (1.10.3), which contains various fixes since the first release candidate

Resources