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

Directory structure of the podman-remote linux tarball is not consistent in 4.4.x releases #18434

Closed
cfergeau opened this issue May 3, 2023 · 1 comment
Labels
kind/bug Categorizes issue or PR as related to a bug. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.

Comments

@cfergeau
Copy link
Contributor

cfergeau commented May 3, 2023

Issue Description

Directory structure of the podman-remote linux tarball (https://github.com/containers/podman/releases/download/v4.4.4/podman-remote-static-linux_amd64.tar.gz) changed several times during the 4.4.x cycle. Sometimes the tarball contains a bin/podman-remote binary, sometimes the bin/ directory is not there.
This makes it inconvenient to consume from crc: crc-org/snc#707

Steps to reproduce the issue

Steps to reproduce the issue

  1. Download https://github.com/containers/podman/releases/download/v4.4.4/podman-remote-static-linux_amd64.tar.gz
  2. Check the archive content
  3. Compare with 1. Download https://github.com/containers/podman/releases/download/v4.4.3/podman-remote-static-linux_amd64.tar.gz

Describe the results you received

Different directory structure between the 2 tarballs

Describe the results you expected

Same directory structure.

podman info output

-

Podman in a container

No

Privileged Or Rootless

None

Upstream Latest Release

Yes

Additional environment details

Additional environment details

Additional information

Additional information like issue happens only occasionally or issue happens with a particular architecture or on a particular setting

@cfergeau cfergeau added the kind/bug Categorizes issue or PR as related to a bug. label May 3, 2023
@Luap99
Copy link
Member

Luap99 commented May 3, 2023

Duplicate of #18215
This should be fixed going forward (#18238).

@Luap99 Luap99 closed this as not planned Won't fix, can't repro, duplicate, stale May 3, 2023
@github-actions github-actions bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Aug 25, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 25, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/bug Categorizes issue or PR as related to a bug. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.
Projects
None yet
Development

No branches or pull requests

2 participants