-
Notifications
You must be signed in to change notification settings - Fork 561
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
header key "followpaths" contains value with non-printable ASCII characters #1058
Comments
The version info from the workflow:
|
I found a workaround here: provenance: false in the |
@andmos Can you enable debug and post logs please? Would be useful to know what's going on: https://docs.docker.com/build/ci/github-actions/configure-builder/#buildkit-container-logs - name: Set up Docker Buildx
uses: docker/setup-buildx-action@v3
with:
buildkitd-flags: --debug Can you also try with latest v0.13 RC of BuildKit if you still repro? - name: Set up Docker Buildx
uses: docker/setup-buildx-action@v3
with:
driver-opts: image=moby/buildkit:v0.13.0-rc3
buildkitd-flags: --debug Thanks! |
@crazy-max sure!
Error only occur when I guess the logs you are after would be from a run without Anyways, here is the debug output from a run with - name: Set up Docker Buildx
uses: docker/setup-buildx-action@v3
with:
buildkitd-flags: --debug And |
Ok that's because If you still want to use - name: Set up Docker Buildx
uses: docker/setup-buildx-action@v3
with:
driver: docker Or like you did disable provenance but it should work with Cloud Run. This is supported for about a year now: docker/buildx#1533 (comment) Closing in the meantime but feel free to continue the discussion. |
Haha here is your repro I think @crazy-max, with - name: Set up Docker Buildx
uses: docker/setup-buildx-action@v3
with:
driver: docker and
So no
I'll build with logs for you. Or, I guess I can't add logging since we're using the docker-driver? |
Yes not possible with docker driver unfortunately. Can you try by adding a step to set up docker engine so we can have docker engine logs: -
name: Set up Docker
uses: crazy-max/ghaction-setup-docker@v3
with:
version: v24.0.9
daemon-config: |
{
"debug": true
}
-
name: Set up Docker Buildx
uses: docker/setup-buildx-action@v3
with:
driver: docker Also check if it works with latest stable docker engine: -
name: Set up Docker
uses: crazy-max/ghaction-setup-docker@v3
with:
version: latest
daemon-config: |
{
"debug": true
}
-
name: Set up Docker Buildx
uses: docker/setup-buildx-action@v3
with:
driver: docker Thanks! |
For some reason I couldn't get any more logs out of it with
now it looks like. |
Good to know! fyi @thaJeztah @vvoland @tonistiigi |
Contributing guidelines
I've found a bug, and:
Description
👋
We're building an application via multistage Dockerfile:
Via
docker/build-push-action@v5
:For deployment on Google Cloud App Engine.
We picked up the project after some months, and the build now fails with
Our codebase has filenames containing the Norwegian
æ
ø
å
, but that has not been a problem before and is not a problem locally. A search for this error returns a fixed BuildKit issue from june 2023: moby/buildkit#3927I've tried to work around the issue by using
buildx
which builds the image without error:But the problem then is that Google Cloud App doesn't support(?):
The image is present in the registry, but the container format is changed:
While the previous working image built without
buildx
had the following:So we're in a bit of a squeeze here, is there some combination of the docker tooling that's not the latest versions on the Github Actions images? We're using
ubuntu-latest
.Expected behaviour
The image should be built without error with files containing non-ACII characters like Æ Ø Å and result in an image artifact with format
Docker Manifest, Schema 2
.Actual behaviour
Repository URL
No response
Workflow run URL
No response
YAML workflow
Workflow logs
No response
BuildKit logs
No response
Additional info
No response
The text was updated successfully, but these errors were encountered: