New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
support building docker images using BuildKit #571
Comments
Hi @helmlover, see the parent issue: docker/for-linux#1136. BuildKit does not yet seem supported over the Docker HTTP API, as such is only currently available via the CLI. |
Hi, |
+1, we need support for this....curious if there a workaround available to achieve the RUN cache like functionality without buildkit features? |
It looks like what's necessary is a support for creating a session and running it in dockerode. Go implementation for that in terraform was added here - https://github.com/kreuzwerker/terraform-provider-docker/pull/387/files#diff-4596d40531ae2e21f6074d104e6dc7317537946b56d95df847c9209dfbe30fceR329 The session run code is here |
The claim "Docker [...] Works out of the box." is no longer true.
That is because docker now uses BuildKit per default, while the BuildKit Dockerfile syntax is not supported when building docker images with testcontainers-node (e.g. with
GenericContainer.fromDockerfile(buildContext).build()
)When building a Dockerfile containing BuildKit-features e.g.
through testcontains-node (with
export 'DEBUG=testcontainers*'
), the output currently looks like:Exporting
export DOCKER_BUILDKIT=1
does not change the problem/output.PS: Sibling issue in testcontainers-java: testcontainers/testcontainers-java#2857
The text was updated successfully, but these errors were encountered: