Skip to content

Conversation

@jlebon
Copy link
Member

@jlebon jlebon commented Jan 26, 2026

This allows defining a dependency on another stage for cases when buildah otherwise wouldn't be able to automatically infer it. See containers/buildah#6621 for details.

The corresponding buildah patch making use of this will have more info.

For now, makes this an explicitly error if used with the dockerclient. I don't see the use case for it there currently given that this flag is to help leverage a buildah-specific feature.

Assisted-by: Claude Opus 4.5

@jlebon
Copy link
Member Author

jlebon commented Jan 26, 2026

CI failure here I think is unrelated. Looks like a Docker API version mismatch.

FWIW, I got this to work locally by setting DOCKER_API_VERSION=1.44.

@nalind
Copy link
Member

nalind commented Jan 26, 2026

This either needs to implement --after for the dockerclient implementation, or add logic to have it error out if the flag is used. We don't want it to just be ignored, giving people a reason to think it'll have the desired effect, when it won't.

@jlebon
Copy link
Member Author

jlebon commented Jan 27, 2026

This either needs to implement --after for the dockerclient implementation, or add logic to have it error out if the flag is used. We don't want it to just be ignored, giving people a reason to think it'll have the desired effect, when it won't.

Updated!

I went with just erroring out for now as mentioned in the commit message:

For now, makes this an explicitly error if used with the dockerclient. I don't see the use case for it there currently given that this flag is to help leverage a buildah-specific feature.

@TomSweeneyRedHat
Copy link
Contributor

@jlebon seems you have a build failure here....

@jlebon
Copy link
Member Author

jlebon commented Jan 27, 2026

@jlebon seems you have a build failure here....

One of them was failing in the conforming tests with what I mentioned in #316 (comment). The other one didn't seem to have any obvious error. It looks truncated?

I repushed to force a retrigger. Let's see what happens...

@jlebon
Copy link
Member Author

jlebon commented Jan 28, 2026

It's persistent. I think CI just needs some love. Looks like that's happening in #317. :)

@jlebon
Copy link
Member Author

jlebon commented Jan 30, 2026

Rebased for CI!

@TomSweeneyRedHat
Copy link
Contributor

Looks to be passing! Are you planning to add a test or two? I could have sworn you had a test when I reviewed the last time....

@jlebon
Copy link
Member Author

jlebon commented Jan 30, 2026

I added a test in containers/buildah#6654, but I can add one here too if desired!

@TomSweeneyRedHat
Copy link
Contributor

@jlebon Yes, please add a test here too.

@jlebon
Copy link
Member Author

jlebon commented Feb 2, 2026

@jlebon Yes, please add a test here too.

Done! Did something in line with what's done for the --platform arg. Let me know if you were thinking of something different.

@nalind
Copy link
Member

nalind commented Feb 2, 2026

LGTM, thanks!

@TomSweeneyRedHat
Copy link
Contributor

LGTM
thanks @jlebon !

This allows defining a dependency on another stage for cases when
buildah otherwise wouldn't be able to automatically infer it. See
containers/buildah#6621 for details.

The corresponding buildah patch making use of this will have more info.

For now, makes this an explicitly error if used with the dockerclient. I
don't see the use case for it there currently given that this flag is to
help leverage a buildah-specific feature.

Assisted-by: Claude Opus 4.5
Signed-off-by: Jonathan Lebon <jonathan@jlebon.com>
@jlebon
Copy link
Member Author

jlebon commented Feb 2, 2026

Sorry, I had screwed up the squashing here when I added tests and had the wrong commit message. Now fixed! Commit content itself didn't change.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 2, 2026

@jlebon: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@jlebon
Copy link
Member Author

jlebon commented Feb 3, 2026

I think this needs actual /lgtm and /approved comments

@TomSweeneyRedHat
Copy link
Contributor

/approved

@TomSweeneyRedHat
Copy link
Contributor

LGTM

@nalind
Copy link
Member

nalind commented Feb 3, 2026

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 3, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 3, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jlebon, nalind

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 3, 2026
@openshift-merge-bot openshift-merge-bot bot merged commit 863d300 into openshift:master Feb 3, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants