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.
Related
I'm trying to install Docker Desktop onto my Windows OS. I have WSL 2 with Ubuntu already set up and have the Virtual Machine Platform also checked in the windows features. My OS build is 19043.1766 which means it should work, and I have tried deleting the Docker related information in the App Data folder to no avail. The first time I installed it, it asked me to log out. Ever since then no matter if I reinstall or restart it will always say Docker failed to initialize. This is my first time downloading it and I have never been able to open the program.
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
I'm brand new to Stack Overflow and the world of containers, so hopefully my questions aren't too silly.
So first I will say that I'm aware that there are other questions similar to the one I'm asking, but I've tried the solutions in all of the ones I've found and they haven't worked for me. If there is another question out there that does have the answer, I'm really sorry for double-asking!
So, background info: I've got a Raspberry Pi 3 running Raspbian, with docker freshly installed. I'm able to pull images down from repositories with no real issues. However, I can't run any of them. I always get the same error (the title of my question). Someone pointed out that it might be because there are mostly 64-bit images in the repositories and I'm running a 32-bit machine, which I thought was the problem. but then I pulled a 32-bit Debian image (the first thing I could find that was 32-bit) and tried to do docker run with the image ID. but it still comes up with that error.
What else may cause that error? Or maybe it's the fact that I'm doing it on a Pi...? Open to anything!
Thanks in advance!
I have had similar issues when I tried to run Docker images on Rasperri Pi. Most of the Docker images are built for x86/x64 architecture. You need Docker-based apps packaged specifically for ARM to run on Raspberry Pi. Hypriot (Based on Debian) is one of the Raspberry Pi images that built for running latest Docker. Check it out here. They also have images specifically built for ARM. Search for hypriot on docker hub.You still may run these images with your current Docker installation, which I did not try.
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?
I have a RedHat 7 instance running Docker 1.6, and am experiencing a problem when loading a custom docker image. The image was created on a Ubuntu 14.04 environment with Docker 1.5. The image has successfully loaded on the RedHat 7 instance in the past, but after having reinstalled docker (along with removing the containers and images) & updated the software on the server, I get the following error when loading in the image tar file:
FATA[0147] Error response from daemon: ApplyLayer exit status 1 stdout:
stderr: write /opt/oracle/product/12.1.0.2/dbhome_1/oc4j/j2ee/home/applications/ascontrol.ear: read-only file system
The image has an oracle database installed, and after running the load many times, the system seems to error on different files in the oracle install directory.
I don't really have any guesses as to why this error is occurring, or why this issue did not occur originally.
It's also worth noting that I attempted to load this image on an RH 6 environment as well, and have noticed the same behavior.