when i run a pipeline in gitlab-runner.i get an error：
#1 [internal] booting buildkit
#1 pulling image moby/buildkit:buildx-stable-1
#1 pulling image moby/buildkit:buildx-stable-1 2.4s done
#1 ERROR: Error response from daemon: manifest for moby/buildkit:buildx-stable-1 not found
------
> [internal] booting buildkit:
------
ERROR: Error response from daemon: manifest for moby/buildkit:buildx-stable-1 not found
my docker version is 18.03.1-ce
gitlab-runner version is v15.8.1
how to fix it?
gitlab-runner is run as a docker container
Probably you have encountered this problem at the stage of image creation. Errors like this occur due to version incompatibility. Choose other versions for your Docker.
Related
I have a tarball image which is built with docker buildx build for platforms linux/amd64 and linux/arm64 with argument --output=type=oci,dest=/some/path. I am not able to go back and rebuild image with --load or --push.
My first question is, how can I push this tarball to an image registry?
And secondly, how can I instantly use this image in my machine which is linux/amd64?
I would be appreciated if anyone can help me on this.
I have tried to import the tarball image using docker import but I got the error below everytime I tried:
docker: Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "submariner-operator": executable file not found in $PATH: unknown.
ERRO[0000] error waiting for container: context canceled
And docker load gives this error:
open /var/lib/docker/tmp/docker-import-1168996138/blobs/json: no such file or directory
I am trying to build docker image from https://github.com/apache/airflow/blob/2.3.2/Dockerfile
This file has a function method defination
However getting below error
Error response from daemon: dockerfile parse error line 76: unknown instruction: FUNCTION
docker version
docker --version
Docker version 20.10.7, build f0df350
It seems things are working in Mac OS but failing on Ubuntu OS
So I have the found the solution to it. Airflow requires Buildkit to build the image because airflow started using features that are only available in Buildkit.
This can be done by setting DOCKER_BUILDKIT=1 as an environment variable or by installing the buildx plugin and running docker buildx build command.
I have Mac OS and macbook air with m1 core. I want to start docker-compose with flink playground (flink 13) docker-compose link from this docs - operations playground
The docker-compose build executed with error
=> ERROR [internal] load metadata for docker.io/library/maven:3.6-jdk-8-slim 3.6s
=> [internal] load metadata for docker.io/apache/flink:1.13.1-scala_2.12-java8 3.3s
------
> [internal] load metadata for docker.io/library/maven:3.6-jdk-8-slim:
------
failed to solve with frontend dockerfile.v0: failed to create LLB definition: no match for platform in manifest sha256:195e9c227ad891282e80602cac2372a3085ecf4ceefbb395558ffe0f7bb0b9aa: not found
ERROR: Service 'client' failed to build : Build failed
The docker file - Dockerfile
Also I tried to execute
docker pull maven:3.6-jdk-8-slim
no matching manifest for linux/arm64/v8 in the manifest list entries
Then I tried to add to Dockerfile
FROM --platform=linux/amd64 maven:3.8-jdk-8-slim AS builder
But there is an exception -
Type org.apache.maven.wagon.providers.http.HttpWagon$__sisu21 not present
And I tried to change the parent image in Dockerfile from maven:3.6-jdk-8-slim to maven:3.8.2-jdk-11-slim or maven:3.8-jdk-8-slim. Build is OK, but after job starting kafka does not receive any message: the command did not show something:
Also I tried to change Flink version to 13.2 from pull request recommendation. But there is no result.
docker-compose exec kafka kafka-console-consumer.sh --bootstrap-server localhost:9092 --topic input
I do not have the same problem with Windows 10.
There has been some discussion of this in the Flink community, and on Stack Overflow. See FLINK-22331, FLINK-13448, and Running Apache Flink 1.12 Jobs on Apple M1 Silicon. There's work being done to prepare an arm64 binary release for Flink 1.14. See the mailing list archive.
I've run into a weird permissions issue in WSL 2 and am struggling to solve it. We have multiple containers that are running in docker via docker compose. Everything was working fine and then I went to run make rebuild with an updated dependencies file and I'm receiving the following exception:
(base) jam#Dagobah-System:~/dev$ sudo make rebuild
Input arguments
REPO: local
CONTAINER TAG: 0
SSH KEY PATH: /home/jam/.ssh/id_rsa
BASE REQS: ./deploy/environment/requirements.base.txt
CUSTOM REQS: ./deploy/environment/requirements.custom.txt
LOCAL REQS: ./deploy/environment/requirements.local.txt
TIMEZONE: Etc/UTC
DOCKERFILE: Dockerfile.local
Building base image
[+] Building 0.0s (1/2)
=> ERROR [internal] load build definition from Dockerfile.local 0.0s
------
> [internal] load build definition from Dockerfile.local:
------
failed to solve with frontend dockerfile.v0: failed to read dockerfile: failed to create lease: write /var/lib/docker/buildkit/containerdmeta.db: read-only file system
Finished building base image
Creating network "dev_default" with the default driver
ERROR: failed to update bridge store for object type *bridge.networkConfiguration: open /var/lib/docker/network/files/local-kv.db: read-only file system
makefile:24: recipe for target 'start-infra' failed
make: *** [start-infra] Error 1
If I close everything out, restart the machine, and I can bring the old containers back up and they run fine. This looks to be some sort of permissions issue between WSL 2, Docker, and the Docker directory on Windows 10 pro.
Windows 10 Pro
Version: 10.0.19041 Build 19041
Shouldn't matter, but the user in wsl has the same credentials as the user on Windows. I also configured Docker for windows with:
Start Docker Desktop when you login
Expose daemon on tcp://localhost:2375 without TLS
Use the WSL 2 based engine
In Console of Google Cloud Platform I try to pull and setup a Docker image:
sudo docker pull nginx:1.10.0 but falling into an error:
~$ sudo docker pull nginx:1.10.0
1.10.0: Pulling from library/nginx
51f5c6a04d83: Extracting [==================================================>] 51.36 MB/51.36 MB
a3ed95caeb02: Download complete
14ef99dba46e: Download complete
3e91b3ec524a: Download complete
FATA[0002] failed to register layer: Untar error on re-exec cmd: fork/exec /proc/self/exe: stale NFS file handle
Is an anybody experienced same issue?