Skip to content
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

Pass platform constraint for oci layout #3397

Merged
merged 1 commit into from
Dec 13, 2022

Conversation

giggsoff
Copy link
Contributor

In case of oci layout FROM --platform= notation does not pass platform
constraint. In case of pointing onto digest of multi-platform index we
try to resolve target platform, which is wrong.

fixes #3396

Signed-off-by: Petr Fedchenkov giggsoff@gmail.com

In case of oci layout `FROM --platform=` notation does not pass platform
 constraint. In case of pointing onto digest of multi-platform index we
 try to resolve target platform, which is wrong.

Signed-off-by: Petr Fedchenkov <giggsoff@gmail.com>
@jedevc
Copy link
Member

jedevc commented Dec 13, 2022

Good catch @giggsoff! I've been playing with the OCI layout code and didn't catch this one myself 😮‍💨

I can see similar logic implemented for docker-container, so I'm happy with the implementation 🎉

@jedevc jedevc merged commit 93b4070 into moby:master Dec 13, 2022
@deitch
Copy link
Contributor

deitch commented Dec 13, 2022

Thank you for the fix @giggsoff and the rapid merge @jedevc

@deitch
Copy link
Contributor

deitch commented Dec 13, 2022

@jedevc when does this end up in moby/buildkit? I am asking both in terms of a moby/buildkit image I can reference directly (i.e. that buildkitd will have this built-in, not just via # syntax=docker/dockerfile-upstream:master, and in terms of semver?

@jedevc
Copy link
Member

jedevc commented Dec 13, 2022

Should be released in v0.11 - we've already done a release candidate RC1, we aim to do a full release soon.

Just a note, API compatibility won't necessarily be preserved between RCs and dev branches, we only have our API compatibility guarantees between our actual releases.

@deitch
Copy link
Contributor

deitch commented Dec 13, 2022

v0.11

Is there an ETA?

In the meantime, I probably can just use a reference to a specific digest, which is what I have done in the past.

API compatibility won't necessarily be preserved between RCs and dev branches, we only have our API compatibility guarantees between our actual releases

Hopefully, I haven't used anything that will break. If I do, we will fix it.

@deitch
Copy link
Contributor

deitch commented Dec 13, 2022

probably can just use a reference to a specific digest, which is what I have done in the past

Am I correct that this tag includes it?

@jedevc
Copy link
Member

jedevc commented Dec 13, 2022

Is there an ETA?

When it's done 😉 Likely sometime this/next month, but can't say for sure.

Am I correct that this tag includes it?

Correct. Likewise with docker/dockerfile-upstream:master for frontend-side changes, like this one.

Hopefully, I haven't used anything that will break. If I do, we will fix it.

Any issues will likely be avoided by making sure that you don't mix and match development versions of buildx/buildkit/dockerfiles.

@deitch
Copy link
Contributor

deitch commented Dec 13, 2022

Cool, thanks.

Looks like it is moby/buildkit@sha256:daadc9f6dc5829c9dfa68ef9f4292c2d5b2fddf848046e02e43db53037373dda, which I can reference.

While on the topic, did the frontend ADD <git> ever make it into anything other than docker/dockerfile-upstream:master-lab?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

oci-layout source ignores platform
3 participants