-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
[containerd] manifest list pointing to schema1 not supported #878
Comments
I'm not quite sure what command you are running. Tried building from We should avoid v1 images for whatever reason in the upload process. They have been discouraged for more than 3 years now and there is absolutely no reason for ever creating them. docker engine codebase still not giving an error for them isn't really an argument. A future version of docker will stop supporting them, the question is only when. |
Thank you for looking at this issue. It seems like golang:1.12-alpine finally got linux/arm64 v2 manifest. At least I can see it executing My
How I start buildkit
How I'm trying to build
|
@moikot I do see the issue with
|
Done |
I can successfully pull arm64/v8 Golang images using
But when I try to build an image specifying arm64/v8 as the platform using buildkit the build fails with error:
error: failed to solve: rpc error: code = Unknown desc = failed to copy: httpReaderSeeker: failed open: could not fetch content descriptor sha256:7cf1f7ccf392bd834eb91f02892f48992d3c2ba292c2198315a4637bb9454c30 (application/vnd.docker.distribution.manifest.v1+json) from remote: not found
I inspected the manifests for golang using
weshigbee/manifest-tool
and it reported that there are no layers for arm64/v8 so I submitted an issue for golang.But the issue was investigated and @yosifkit found out that it was a glitch on Github and some manifests were pushed as v2 and some as v1 and an issue was raised for manifest-tool too.
Would it be possible to handle such situation, when some manifests are using v2 and some v1, correctly in buildkit?
The text was updated successfully, but these errors were encountered: