buildx: failed to solve with frontend dockerfile.v0: failed to build LLB: executor failed running - runc did not terminate sucessfully

Mac Catilina Docker Version: 2.4.0.0

Docker file

ARG ALPINE_VERSION
ARG PHP_VERSION
ARG SECRETS_PARAM_NAME

FROM alpine:${ALPINE_VERSION} as python
RUN apk --no-cache --update add \
  py-pip && \
  pip install --upgrade awscli

FROM madnight/docker-alpine-wkhtmltopdf as wkhtmltox

FROM php:${PHP_VERSION}-fpm-alpine${ALPINE_VERSION}

VOLUME ["/app/webroot"]

RUN apk --no-cache --purge --update add \
    --virtual .build-deps \
    autoconf \
    build-base \
    libtool && \
  apk --no-cache --purge --update add \
    --virtual .persistent-deps \
    py-pip  \
    freetype-dev \
    gnumeric \
    icu-dev \
    imagemagick \
    imagemagick-dev \
    jq \
    glib libcrypto1.0 libgcc libintl libjpeg-turbo-dev libssl1.0 libstdc++ libx11 libxext libxrender \
    libmcrypt-dev \
    libpng-dev \
    postgresql-dev \
    postgresql-client \
    python2 \
    ttf-dejavu ttf-droid ttf-freefont ttf-liberation ttf-ubuntu-font-family && \
  docker-php-ext-configure gd --with-freetype-dir=/usr/include/ --with-jpeg-dir=/usr/include/ && \
  docker-php-ext-install gd intl opcache pdo_pgsql mcrypt zip && \
  pecl install apcu imagick xdebug && \
  docker-php-ext-enable apcu imagick && \
  pip install --upgrade awscli es2csv && \
  apk del .build-deps && \
  rm -rf /root/.cache && \
  rm -rf /tmp/*

COPY --from=python /root/.cache /root/.cache
COPY --from=wkhtmltox /bin/wkhtmltopdf /usr/local/bin/wkhtmltopdf
RUN ln -s /usr/local/bin/wkhtmltopdf wkhtmltopdf

COPY php/ini/*.ini  /usr/local/etc/php/conf.d/
COPY php/fpm/*.conf /usr/local/etc/php-fpm.d/

ENV SECRETS_PARAM_NAME ${SECRETS_PARAM_NAME}
COPY dms-entrypoint /usr/local/bin/
ENTRYPOINT ["dms-entrypoint"]
CMD ["docker-php-entrypoint", "php-fpm"]

About this issue

Original URL
State: closed
Created 4 years ago
Reactions: 10
Comments: 39 (9 by maintainers)

Links to this issue

docker - An error, "failed to solve with frontend dockerfile.v0" - Stack Overflow

Most upvoted comments

same issue…any fix??

Don’t use buildkit and it works for me.

export DOCKER_BUILDKIT=0
export COMPOSE_DOCKER_CLI_BUILD=0

+285

adrubesh on Apr 6, 2022

It happens during build, my best guess is it’s a bug in buildkit, which is fine considering buildkit still isn’t stable yet. The two exports I mentioned above disable buildkit in your shell environment. If you are using Docker desktop for Mac / Windows you might have to also disable it in your ‘Docker Engine’ json config. Docker desktop -> Settings -> Docker Engine -> Change the "features": { buildkit: true} to "features": { buildkit: false}.

Note, this isn’t a FIX, this is a workaround until someone on the docker teams implements a proper fix. Please give buildkit another shot when it’s a little more stable 😃

+44

adrubesh on Nov 24, 2020

export DOCKER_BUILDKIT=0 export COMPOSE_DOCKER_CLI_BUILD=0

This worked for me @janpauldahlke

+26

kushthedude on Nov 24, 2020

I think we should close this issue to not confuse new people. Only report that provided full error output is https://github.com/docker/buildx/issues/426#issuecomment-731555478 and that one clearly is a temporary application error.

2020-11-21T09:44:55.6953810Z #13 68.41 verifying github.com/prologic/bitcask@v0.3.6/go.mod: checksum mismatch
2020-11-21T09:44:55.6954724Z #13 68.41 	downloaded: h1:WQuqL23CGZcC83DhKuXH6KMHe1m25+Eb43s8yM3MnF0=
2020-11-21T09:44:55.6955673Z #13 68.41 	go.sum:     h1:lGs61R8cREh1Wq/O+eErqTdGmsaen7cDxu3Zdbs9xBA=
2020-11-21T09:44:55.6956221Z #13 68.41

This is just a prefix that appears is any error that happens in your application logic inside the container. Eg. a bug, external service misbehaving or network flakiness. If the failing process produced logs for the error they are shown above it.

If you do see it and can’t figure out the cause from logs, open an issue with a reproducer and full logs output.

Other than making the error message more clear there is nothing to work on here atm.

+11

tonistiigi on Nov 24, 2020

I disabled Big Sur virtualization framework and it worked

tudor-pop on May 18, 2021

You need to add into your terminal where you are building your docker image.

kushthedude on Nov 24, 2020

I also had to set

DOCKER_BUILDKIT=0

when using macOS Docker 3.1.0

bixu on Feb 24, 2021

It happens during build, my best guess is it’s a bug in buildkit, which is fine considering buildkit still isn’t stable yet. The two exports I mentioned above disable buildkit in your shell environment. If you are using Docker desktop for Mac / Windows you might have to also disable it in your ‘Docker Engine’ json config. Docker desktop -> Settings -> Docker Engine -> Change the "features": { buildkit: true} to "features": { buildkit: false}.

Note, this isn’t a FIX, this is a workaround until someone on the docker teams implements a proper fix. Please give buildkit another shot when it’s a little more stable 😃

Great ! Nothing new, just adding the Docker documentation explaining the same :

https://docs.docker.com/develop/develop-images/build_enhancements/#to-enable-buildkit-builds

ghusta on Mar 11, 2021

export DOCKER_BUILDKIT=0 export COMPOSE_DOCKER_CLI_BUILD=0

This worked for me @janpauldahlke

How did you fix? I am stuck in build “Push Docker Image to Github Packages”. I am newbie at Github Actions

@EmreErinc In the run part of the action add the above export lines like done here https://github.com/layer5io/meshery/blob/0049d3eef50666352e40ac6706ac08d8138f0da3/.github/workflows/build-and-release.yml#L53

kushthedude on Nov 24, 2020

I disabled Big Sur virtualization framework and it worked

it works. but hyperkit is very power-consuming, high CPU usage, and heat generation.

Diluka on Jun 7, 2021

export DOCKER_BUILDKIT=0 export COMPOSE_DOCKER_CLI_BUILD=0

I’m using windows10, Hyper-V, this works for me!

brownchow on Dec 8, 2020

Ah, sorry, my comment crossed your previous comment

thaJeztah on Nov 24, 2020

plus I think registry won’t matter here as this is happening in the build step rather than push to registry step 😅

thx! mostly checking, because the “old” github image registry is known to be largely broken (as it only implements parts of the distribution (registry) specification; https://github.com/moby/moby/issues/41687)

thaJeztah on Nov 24, 2020

@kushthedude Great man, it instantly worked now. I will add those lines to my README.md. ty bro. BTW: is there any explanation why this occurs?

Looks like a bug in the latest BUILDKIT, am still not sure. @adrubesh may have more info on it

kushthedude on Nov 24, 2020

@SeanFacer I was facing a similar issue. What really worked for me was

Stop the containers using the docker image
Remove the volumes used by the containers

Rebuild the image.

Alternatively, tag the build image with suffix abc:1.x

riteshgurung on Oct 29, 2020