-
Notifications
You must be signed in to change notification settings - Fork 785
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
[Feature]: Add support for "buildx build --push" and/or "buildx build --output=type=registry" #4671
Comments
Would love to get a commit from you. |
A friendly reminder that this issue had no activity for 30 days. |
@flouthoc got some time to look at this? |
I'll take a look at this. |
@flouthoc If you haven't started already, I'd like to take a shot at this. |
@danishprakash Sure feel free to take it. |
@danishprakash In case if you go short on time, feel free to assign it back to me anytime :) |
Just starting here but shouldn't this be moved to containers/buildah given the actual changes would be made there and perhaps the flags to be moved here once that's done? Or am I missing something? |
A friendly reminder that this issue had no activity for 30 days. |
@danishprakash @flouthoc What is the state of this one? |
Could you take a look at some of my comments on the PR for this? Whenever you've a moment, thanks! |
A friendly reminder that this issue had no activity for 30 days. |
Being Implemented here: #4677 |
A friendly reminder that this issue had no activity for 30 days. |
Feature request description
Please add support for the "buildx build --push" and/or "buildx build --output=type=registry" flags which would ensure that the built image is pushed to the registry. According to the buildx reference, the
--push
flag is just shorthand for--output=type=registry
. So IMHO implementing both these things would be ideal, but I will be happy with either one.Suggest potential solution
A clear and concise description of what you want to happen.
Have you considered any alternatives?
When using the CLI manually, I can of course use a separate command to push the image, this feature would help in integration with other tools - I am using DevSpace CLI tool which, in some cases, calls
docker build build
via CLI, and it relies on the--push
flag. And so far this is the only compatibility problem that I found when using podman(with podman-docker).Additional context
I may be able to contribute a PR if you think this is not to complex, and can give me a couple of pointers in the right direction. :)
The text was updated successfully, but these errors were encountered: