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?
Related
I set up a Windows GitLab runner that's supposed to download a Docker image from our Container Registry and then run a build script in the pipeline. Unfortunately the Docker container never launches due to the following error:
Running with gitlab-runner 15.1.0 (76984217)
on WindowsDockerRunner wZMWQZYi
Resolving secrets
Preparing the "docker-windows" executor
Using Docker executor with image mcr.microsoft.com/windows/servercore:ltsc2019 ...
Pulling docker image mcr.microsoft.com/windows/servercore:ltsc2019 ...
Using docker image sha256:e6b07227af5ca9303c2112b574f6f27f38135bbf9df29d829142410221967401 for mcr.microsoft.com/windows/servercore:ltsc2019 with digest mcr.microsoft.com/windows/servercore#sha256:26c6c296a4737ba478fe3c3e531b098f89b5562c40b416ba6fb8177ac462d1af ...
Preparing environment
Running on RUNNER-WZMWQZYI via
runner2...
ERROR: Job failed (system failure): prepare environment: Error response from daemon: invalid condition: "not-running". Check https://docs.gitlab.com/runner/shells/index.html#shell-profile-loading for more information
The error message doesn't clearly state what the cause of the problem is and the documentation that it references doesn't mention anything about "condition". Based on the link pointing to shell profiles I suspect it might have something to do with the shell that's being run, but when I run the Docker container locally it boots into PowerShell just fine.
Does anyone know how to solve this?
I came across this issue after installing Docker Engine using the Windows Server install script, which fetches docker.exe and dockerd.exe from https://master.dockerproject.org, These builds were last updated in March 2022, I found gitlab-runner 14.9 and earlier work okay with this version (released prior to March 2022), but 14.10 does not (released 2022-04-19) nor do any newer versions.
Installing Docker Desktop resolves this as it provides the latest version. However using Docker Desktop introduces licensing issues. An alternative is to manually install Docker Engine / update the version downloaded by the Microsoft script.
Docker Engine builds are provided on the Moby GitHub project to download from https://download.docker.com/win/static/stable/x86_64/ downloading the lastest version from here and replacing the docker executables in C:\Windows\System32 fixes the problem, working with the latest gitlab-runner.
An alternative is to use the docker-engine chocolatey package (which incidentally I maintain) which provides installation scripting for the above stable builds:
choco install docker-engine
There is also an open issue with the Windows-Containers team to move off (out of date) nightlies: https://github.com/microsoft/Windows-Containers/issues/256 which would provide a stable docker build, through the Microsoft recommended installation method.
Was finally able to solve this issue. We had the Docker Engine installed on our GitLab Runner, but that doesn't seem to be sufficient for GitLab CI/CD. After installing Docker Desktop on the runner the issue disappeared and we were able to run the pipeline.
After some trial and error I got it up and running.
I have another server running the gitlab-runner and docker without any issues (no docker desktop installed, which is not allowed because of licensing stuff).
The server I'm trying to setup right now is a 'redundancy' build server.
So to find out what was my problem, I started switching things from one build server to the other. Currently, it appears that simply downgrading to the gitlab-runner V13.4.0 was enough.
I did reregister the runner, since gitlab stated that the V15.x.x version was using executor "unknown".
Not sure what is going on there, but at least I can continue building now.
Thanks so much in advance for taking the time to read/provide any advice here.
So, I am trying to get an instance of MISP running through docker. The hardware I have it running on is a raspberry pi 4 running Ubuntu 20.04 (server edition).
I thought I installed all software dependencies, but being new to using docker, perhaps I haven't. I'm using this repository for the docker image: https://github.com/MISP/misp-docker
After running the command sudo docker-compose up after copying the .env file to the root directory, I get the error that I am going to post an image of below along with the text of the error for easy copy/pasting
ERROR: Service 'web' failed to build: The command '/bin/sh -c bash INSTALL_NODB.sh -A -u' returned a non-zero code: 1
ERROR MESSAGE SCREENSHOT
Once again, thank you all for any and all help! Please let me know if I can provide any more information!
Looks like this may be an issue that was closed in May of 2021 https://github.com/MISP/MISP/issues/7375. That Docker image has an INSTALL_NODB.sh that was initially committed in March 2021 https://github.com/MISP/misp-docker/commit/1e2f18f2c1211e382bd8df5371b1d3d718dad061. Since it was added before that fix the container may not include the fix for rpi that was added in the main repo. To verify, you can check if the output of uname -m is in this support map from the script used by the docker image https://github.com/MISP/misp-docker/blob/master/web/INSTALL_NODB.sh#L3070. If it isn't, then you would need this fix implemented in the docker image.
aarch64 isn't a supported architecture. There's a pull request on the repository that adds it, so you can add that change to your local repository like this (from a command line in the misp-docker repository):
git remote add fukusuket https://github.com/fukusuket/misp-docker.git
git fetch fukusuket
git merge fukusuket/hotfix/build-error-on-m1-mac -m "add aarch64 support"
Hopefully the pull request will be accepted soon and then you can go back to using the unaltered MISP git repository.
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 run the following command to deploy a new cluster:
docker run --net=host -t -e LICENSE=accept -v "$(pwd)":/installer/cluster ibmcom/icp-inception:2.1.0.2-ee install
and i get this response:
Unable to find image 'ibmcom/icp-inception:2.1.0.2-ee' locally
docker: Error response from daemon: manifest for ibmcom/icp-inception:2.1.0.2-ee not found.
See 'docker run --help'.
This happened about a couple of weeks ago, and when i did nothing other than wait a few days and tried again, the command worked. It is as if the tag, 2.1.0.2-ee is not accessible. indeed, when i go to docker hub, i don't see that tag listed. But then i'm a newbie with docker hub so I'm not sure if i'm interpreting this correctly.
is it me, or is ee not available to all? i could do a docker pull with ce, no problem.
Thanks
It isn't you! ibmcom/icp-inception:2.1.0.2-ee points to the paid-for version of IBM Cloud Private and is not distributed through DockerHub. We distribute our community edition, ibmcom/icp-inception:2.1.0.2-ce, (which is free to use) via DockerHub, which is why you are not having any issues with ce.
The only difference you will find between Community Edition and Enterprise Edition is that multi-master deployments and production are not enabled in Community Edition.
Let me know if you have any further questions.
Thanks everyone on slack and stack overflow.
My mistake was that the snapshot that i took just prior to deploying the cluster successfully was not what i thought.
i think i must have checkpointed prior to loading ee into docker rather than just before running icp-inception.
It makes sense that icp ee is not publicly downloadable.
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