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.
Related
I am having issues trying to open Docker on Windows 11 after installing. I followed the instructions on the Docker website, and have a working WSL 2 installation. When I try to open Docker Desktop, the application first shows a red banner that says "Unable to calculate image disk size" and then freezes. Docker Desktop does not have a storage size listed in the app list.
During the installation process, I do not see se WSL 2 instead of Hyper-V option on the Configuration page. When I run the command ".\resources\com.docker.diagnose.exe check", I get the following error message (edited for brevity):
failed to ping VM diagnosticsd with error: Get "http://ipc/ping": open \\.\pipe\dockerDiagnosticd: The system cannot find the file specified.
I can provide the full message if need be but Stack Overflow keeps marking this post as spam. I have looked online for potential solutions but none have worked. I have tried uninstalling and reinstalling, modifying $PATH, pruning Docker, running Docker outside of Docker Desktop.
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 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.
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.
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?