-
Notifications
You must be signed in to change notification settings - Fork 500
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
grpc: failed to unmarshal the received message: string field contains invalid UTF-8 #2850
Comments
Upgrading from what version? Please post reproduction steps. |
Hello, we get the same problem since an upgrade this WE. 27.3.1 -> 27.4.1
version that works with the same build:
version that FAILS with the same build:
if we can help pinpoint the problem, please ask |
some tests i did:
so for me, it's only happening while docker compose build is running under the gitlab-ce runner hood, on a debian bookworm host with latest docker-ce packages (as of today) again, if i can test something else, just ask |
@tonistiigi Any progress? |
My best guess is that you have something in the build context that makes the paths or symlink fields in https://github.com/tonistiigi/fsutil/blob/master/types/stat.proto#L10-L17 contain values that are not strings. Not sure what case would do that but likely that our validation that these are actual strings and not non-printable bytes is more strict now. |
After checking, it was found that some file names were indeed not encoded in UTF-8, but in GB2312. |
i confirm it's related to a filename encoding. |
Do you have a practical testcase for this, so we can look if there is a way to mitigate with workaround or improve error. |
After upgrading to buildx version v0.19.2, the following error is reported when building the image
version info:
The text was updated successfully, but these errors were encountered: