Provide both x86_64 and aarch64 binaries for podman-remote-linux #16612
Labels
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
Comments
|
@mheon @ashley-cui FYI |
|
@cfergeau interested in opening a PR? |
cfergeau
added a commit
to cfergeau/podman
that referenced
this issue
Nov 29, 2022
This is more consistent with the name of the other released files, and makes identification of the binaries easier among the Windows/macOS ones. Related: containers#16612 Signed-off-by: Christophe Fergeau <cfergeau@redhat.com>
cfergeau
added a commit
to cfergeau/podman
that referenced
this issue
Nov 29, 2022
All files released in https://github.com/containers/podman/releases/tag/v4.3.1 use -arm64 for the arch name except podman-installer-macos-aarch64.pkg Related: containers#16612 Signed-off-by: Christophe Fergeau <cfergeau@redhat.com>
github-actions
bot
added
the
locked - please file new issue/PR
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
If I go to https://github.com/containers/podman/releases/tag/v4.3.1 there are aarch64/arm64 and/or amd64 files for macos and Windows, and a lone podman-remote-static.tar.gz file. This one was an aarch64 binary for the 4.3.0 release, and is a x86_64 binary for the 4.3.1 release. Can it be renamed to podman-remote-static-linux_amd64.tar.gz, and can an _arm64 binary be provided alongside of it?
Also note the inconsistent arch names for macOS:
podman-installer-macos-aarch64.pkg and podman-remote-release-darwin_arm64.zip
The text was updated successfully, but these errors were encountered: