-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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 Request] Create container image which have podman-remote binary for all platform and arch #14664
Comments
If we had quay.io/podman/stable available for multi-arch, wouldn't this achieve the same thing, since you can execute podman -remote from within these containers? |
@rhatdan yes having it as multi-arch helps. Executing |
A friendly reminder that this issue had no activity for 30 days. |
I would suggest you open a PR to create such an image. |
@rhatdan Sure, l will try to put a PR and see how it goes. |
A friendly reminder that this issue had no activity for 30 days. |
@praveenkumar were you able to work on this? |
@rhatdan Not yet :( , let me pick it up during this week (it is learn week). |
Try to partial address containers#14664 Signed-off-by: Praveen Kumar <[email protected]>
Since #15813 merged, we can close |
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind feature
Description
As of now we release the podman-remote binary https://github.com/containers/podman/releases/tag/v4.1.1 it would be good if we have those binaries (not the msi) as part of single container image (something like podman-remote distribution image) which can be triggered during any PR on specific branch/tag or even master and always updated. This will help podman-remote consumer to not depend on the release bits if some bug introduced to it like #14201 one and fixed on main branch so able to consume the nightly container image.
This should be something similar what OpenShift client binary (oc) have as a single container image consist of all platform binaries.
The text was updated successfully, but these errors were encountered: