I have installed boot2docker in my windows 7 64 bit box (Docker Version: 1.3.0). But I'm not able to pull any public images, and it shows the below error message.
Command :docker pull java.
Result:
Pulling repository java.
Could not reach any registry endpoint.
But, I can able to perform other command successfully. Like Search, List of installed images (In my case it's 0).
Can somebody help me to overcome this issue?
Related
I'm attempting to create a Docker image with a MarkLogic RPM file installed (based on CentOS7). I successfully created some images like this earlier, but now it fails every time. I got this error:
Step 5/7 : COPY MarkLogic-RHEL7-8.0-5.2.x86_64.rpm /tmp/MarkLogic.rpm
failed to create rwlayer: devicemapper: Error running deviceCreate (CreateSnapDeviceRaw) dm_task_run failed
I saw this question and the MarkLogic RPM is fairly large (139MB), so I purged all unneeded images. Since I work in a Linux VM, I increased the drive space to 50GB, so now I have 35GB free. But trying it again, I still get the same error. Even though the MarkLogic RPM is pretty hefty, I should have plenty of space to create the image now.
Anyone know the real source of the error and how to overcome it?
Using Docker 18.09.0 and CentOS 7.6.
I worked directly with MarkLogic on this issue. While they do officially support Docker now, it is only officially supported for versions 9.0-5 and above. Since i was using version 8.0-5.x, it's not surprising it didn't work. Following the instructions here, I was able to successfully create a MarkLogic Docker image, run it as a container and connect to it.
C:\Users\mites>docker pull busybox
Using default tag: latest
latest: Pulling from library/busybox
no matching manifest for unknown in the manifest list entries
How to solve this ? it occours up on every pull command.
I was running my app on Windows 10 Pro, Docker CE, windows containers when I got this error.
I switched to using linux containers and it resolved this issue for me.
Note: I was using python, reddis in this scenario for my app.
Hope this helps someone.
I had the same problem on my Windows 10 Pro.
While checking the docker logs I found more explanatory log entries:
[09:32:42.958][WindowsDaemon ][Info ] debug: a Windows version 10.0.17763-based image is incompatible with a 10.0.17134 host
[09:32:42.958][WindowsDaemon ][Info ] debug: no matching manifest for unknown in the manifest list entries
The solution was to update my Windows 10 Pro installation to a later version. After that, I was able to pull the image from the repo.
I'm trying to load an image on my Windows Server 2016. But for some reason I'm unable to do so. I have tried several things. Including:
Saving an image, copy pasting it to the server and trying to load it (docker load...). This gives the error you see down below. I also tried to load the image through docker hub. But using docker pull gives me the exact same error.
I've tried pulling other images like microsoft/windowsservercore which was successful. On my development machine and server I'm using windows containers. The windows server runs in a virtual machine.
I've created a sample project on https://hub.docker.com/r/sbrauer/dockert/.
This project is just a asp.netcore web api project with the default 'valuescontroller' as a test. But this gave me the same error.
I have to say that pulling the image to my dev machine (w10) works perfectly fine. I tried to load the image on the server using docker CE and using docker EE but both to no avail.
error code:
failed to register layer: re-exec error: exit status 1: output:
ProcessUtilityVMImage C:\ProgramData\Docker\windowsfilte
r\13f0d09f57da5375955d3563b3a199fd1f3563365abe5b31640eee885aac448a\UtilityVM:
The system cannot find the path specified.
Thanks for any help in advance.
I'm trying to create docker containers in a Windows 10, but it always gives me the following
"failed to register layer: rename C: ....."
I can not find any thread to explain it, I´ve executed PS as a Administrator
I put the trace of the pull:
PS C:\WINDOWS\system32> docker pull microsoft/aspnet
Using default tag: latest
latest: Pulling from microsoft/aspnet
9c7f9c7d9bc2: Pull complete
d33fff6043a1: Pull complete
b7c3bbe47489: Extracting [==================================================>] 123.8 MB/123.8 MB
1028e286eae2: Download complete
28e6f26ee039: Download complete
a0db4e322336: Download complete
failed to register layer: rename C:\ProgramData\Docker\image\windowsfilter\layerdb\tmp\write-set-255580435 C:\ProgramDat
a\Docker\image\windowsfilter\layerdb\sha256\b01351fac2d37b162190ef8dde977bbf009d8e3fa2446dd71595b142b73d28a3: Denied Access
Someone knows what´s the reason?
Thanks in advance.
OK I have been struggling with this little devil for a while now. I have windows containers working on my desktop, but on my new laptop it was giving me a hard time.
I have changed permissions on all the C:\ProgramData\Docker folder at the beginning, to no avail.
After a while I realized that there IS a difference between my desktop and the new laptop was the fact that the laptop came preinstalled with McAfee Antivirus. Now I'm not sure if it's a mcafee only issue, or in general antivirus, but when I disabled realtime scanning for a bit, I was able to download the new image without issues.
Restarting Docker Desktop as Administrator worked for me. Before and After Restart
I have installed Airflow with docker on windows. But while pulling image of Airflow I am facing same issue and I had resolved this issue by switch the container to Linux
I had installed Airflow with docker on windows and I am also facing same issue while start the airflow using following command "docker-compose -f .\docker-compose-LocalExecutor.yml up -d". But I had resolved this issue by switching container to Linux
EDIT: A huge thank you #mattmoor for helping me debug the issue. After I had to create a new docker-machine. There was a problem with the docker daemon that must've arisen due to the first machine not being created correctly.
I am having trouble pulling images from another computer, both of which are running OSX Yosemite. Both machines have the docker daemon running, and have successfully authenticated with the desired project to pull from with
gcloud auth login
On my computer I am able to run:
gcloud docker pull gcr.io/projectid/image-tag without any issues.
However when I try to repeat this on another machine, I get a large error message that begins with:
Error pulling image (tag-here) from gcr.io/projectid/image-tag, endpoint: https://gcr.io/v1/, Untar exit status 2 unexpected fault address 0xc208ce5d04
fatal error: faultr downloading dependent layers
[signal 0xb code=0x1 addr=0xc208ce5d04 pc=0x94109e]
Followed by a goroutine 1 stack trace.
The docker version on both machines is 1.6.2, the client and server api version is 1.18, both Go versions are go1.4.2
The Google Cloud SDK version on both machines is 0.9.67, and both have the following components installed:
bq 2.0.18
bq-nix 2.0.18
core 2015.06.30
core-nix 2015.06.02
gcloud 2015.06.30
gcutil-msg 2015.06.09
gsutil 4.13
gsutil-nix 4.12
preview 2015.06.30
and the machine that works also has these extra components installed:
alpha 2015.06.30
beta 2015.06.30
kubectl
kubectl-darwin-x86_64 0.18.1
Any help would be greatly appreciated, I'm truly baffled as to why I can't pull from the gcr registry on the other machine.
I'm baffled too, this looks like Docker dying trying to untar the blob, and I haven't seen that before.
Would you mind starting a thread with gcr-contact#google.com, as this may take a little debugging, and email will be a bit easier for the back-and-forth.
We can update this with what we find, if that works for you?