Open nudgegoonies opened 1 month ago
@nudgegoonies : Could you please provide more information on how to reproduce it? Could it be related to your Docker version? We have E2E tests that pull images on every run.
fyi: no active sessions
is the error message you get from dockerd if you're trying to use buildkit without active grpc session.
For buildkit support the client (i.e. d-m-p
) has to initialize a grpc sessions (see: Initialize interactive session API). As so far as i know d-m-p
did not implement this Session API for now.
see: this comment
@nudgegoonies : Are you using BuildX functionality?
Yes, we use buildx functionality since it became the default last year. Especially the copy --chmod and --chown on one line.
@nudgegoonies : Does your project work with v0.44.0 ?
Is it possible to share a sample Dockerfile that can reproduce the issue? I ran integration tests with Docker 27.1.1 and they seem to be passing
@rohanKanojia i have taken a closer look on what @nudgegoonies is doing (fyi: we are working in the same organization) and i think we identified the root cause of the "regressions":
version
to 2
(this was intentional because the classic builder doesn't support the full Dockerfile syntax)v0.45.0
the build does not longer work due to the mentioned exception.build.dockerFile
) but the image defined in build.from
configuration.build.from
and build.dockerFile
are both defined in the image configuration. The first on is explicitly defined, but the latter one was inherited from the parent POM.@rroesch1 already figured out the details. To answer the explicit question. Yes, it works with 0.44.
Description
Since version 0.45 the build of an internal project using an internal docker repository (Artifactory) fails pulling the base image used in our Dockerfile processed by docker-maven-plugin. Managing the plugin back to 0.44 is our current workaround.
The maven build log part:
Info
mvn -v
) :