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.
Related
I have Windows Docker Desktop, my os is Windows 10 enterprise , version 20h2
Docker for windows working... i have a small mvc asp.net3.1 application.
I create my docker image and i am able to run the container locally.
Everything is working from my local.
Now i uploaded the image to AWS ECR, create my taskDef and service.
Unfortunatelly the task does not start with the error :
failed to create new container runtime task: failed to create shim: hcs::CreateComputeSystem 95cade147ae4418ab3d68ea1a2c70800-2341308736: The container operating system does not match the host operat
I have seen some compatibility list from microsoft on the OS https://learn.microsoft.com/en-us/virtualization/windowscontainers/deploy-containers/version-compatibility?tabs=windows-server-2022%2Cwindows-11-21H2
I check i have hyperv and all..
Does anyone know how i can make the image compatible? This seems to be a known issues, but i am kind of blocked here.
Thanks
The error indicates you have a different image version versus the host version. What is the base image on your dockerfile? And do you know what is the host version on your AWS environment? For reference, here's the documentation on host compatibility: https://learn.microsoft.com/en-us/virtualization/windowscontainers/deploy-containers/version-compatibility?tabs=windows-server-2022%2Cwindows-11-21H2
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.
We are using Windows OS 7 to develop an application using tech stack viz. docker, spring, java8, gradle etc. We have installed the docker toolbox on our machine.
Now the base image is located in our docker repository of our organization. But the docker is not able to identify the host.
We are able to connect to our repository from docker installed on a linux machine. In that case we have made changes in these 2 files viz.
1.
/etc/systemd/system/docker.service.d/daemon.conf
here we have added http_proxy and https_proxy.
2.
/etc/docker/daemon.json
here we have mentioned the host name as
{"insecure-registries":["<host-name>"]}
But we are not able to find these files in docker tool-box in windows 7.
Please let us know how to resolve this issue.
We are getting the following error in dockerBuildImage gradle task currently wherein it is not able to download the base image.
:dockerBuildImage FAILED
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':dockerBuildImage'.
> Could not build image: Get https:<host-name>/v2/: x509: certificate signed by unknown authority
Please advise.
The following worked for me in docker toolbox
change the file /var/lib/boot2docker/profile to include following text:
--insecure-registry=<host1-name>
export "NO_PROXY=<host-name>"
export HTTP_PROXY=<value>
export HTTPS_PROXY=<value>
Then restart the docker-machine to make these changes visible.
I am working on a windows 10 home so I have a docker toolbox and am using an IBM cloud app service : python-django app. I followed all the instructions given here:
https://console.bluemix.net/docs/apps/tutorials/tutorial_web.html#before-you-begin
I then open it in Pycharm (community edn) and try to build it locally by doing the following :
1)Import the settings.jar file (Given in the developer tools)
2)Tools > IBM Cloud Developer Tools > Build app in release mode
But I get the following error :
Creating image latestpy-django-tools based on Dockerfile-tools...
Building...
OK
Creating a container named 'latestpy-django-tools' from that image...
FAILED
An error Error response from daemon: invalid mode: /app was encountered while creating Docker container 'latestpy-django-tools'.
Please help!!
Kiera.k, on your Win10 system do you have Docker Toolbox or Docker for Windows? IBM Cloud Developer Tools requires Docker for Windows and will not work with Docker Toolbox.
Also, running build with the additional --trace parameter might provide some more details, if you have not already been using that. If you are using Docker for Windows, seeing all the output you get with --trace would be great.
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.