-
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
v4.0.0 missing static binaries in Release page #13298
Comments
I was told not to build them yet by @baude - I'll defer explanation as to why to him |
@mheon thanks a lot for your prompt reply (on a Sunday 😄 ). It's OK if there's short delay, however the Readme should maybe not mention that the static binaries are available then (IMO) |
@nunix The reason why is they are unusable at this point unless the backend is Linux. As with podman 3, podman3 remote clients must connect to podman3 backends. Podman4 must connect with Podman4 backends. Given that FCOS does not ship Podman4 yet, the mac client is not much help (unless connecting to you your Linux backend). You could also compile the client as well. They can be cross-compiled if you like. Bottom line, we should have a better answer mid-werrk. |
@baude thank you for the detailed answer, totally understandable. I will compile the Again, my point was more the misalignment between the repo Readme stating the static binaries were already available and not finding them on release page. But sincerely all good, this case for me can be closed, or kept open just to avoid duplicates (if any) until the binaries are available. Thanks again, and have a great rest of Sunday 😄 |
When I run the release version, the client says "4.0.0-dev" and the server says "4.0.0-rc5" https://github.com/containers/podman/releases/tag/v4.0.0
But it doesn't seem to be using any podman3 backend, even if it is based on Fedora 35 ? var Version = semver.MustParse("4.0.0-dev")
|
I think the server is still waiting for packages to go stable so we can update the VM images. The client is concerning, though. |
I think it accidentally tagged the commit before the version bump... |
Uh-oh. You are entirely correct. I can recreate the tag from the correct commit, but that could confuse things? |
It happens... I guess it will be fixed in 4.0.1, and it doesn't have much to do with the static |
@mheon this also meant that Podman 4.0.0 still uses the 3.3.1 API (not 4.0.0 API) |
Yep, we realized that yesterday. Current plan is to cut a 4.0.1 tomorrow, to give a bit of time for critical issues to emerge (if they're going to). |
Perhaps it is obvious, but is not only in the readme. The download link for Windows on the |
I don't think a new issue for "v4.0.1 is also missing static binaries in Release page" would help ? https://github.com/containers/podman/releases/tag/v4.0.0 https://github.com/containers/podman/releases/tag/v4.0.1 Probably people should just be patient and wait for 4.1, and continue to run 3.4 in the meantime... 🤷 https://github.com/containers/podman/releases/tag/v3.4.2 (latest deb package on Kubic) https://github.com/containers/podman/releases/tag/v3.4.4 (latest podman-remote static) |
I don't think so, but I think it honestly would help if this was clearly announced both on the release notes and on the README of the project, just to set expectations correctly. and avoid these sorts of issues being opened.. |
I think static builds for |
Nope, like @baude explained in a comment on this same issue here, podman-remote (the client) depends on the podman (server), and FCOS (Fedora CoreOS, the distro that's used on the virtual machine that podman-remote manages) wasn't updated yet to v4.0. IMHO what could be released is the podman (server) versions for every distro, but at least on Ubuntu-side like #13302 explains the Kubic repository will not be maintained anymore, so...yeah. It's a complicated situation. |
I understand that it is some kind of weird side-track, but I did think that it was "released" as in "out there". It ( $ podman-remote version
Client: Podman Engine
Version: 4.0.1
API Version: 4.0.1
Go Version: go1.17.2
Git Commit: c8b9a2e3ec3630e9172499e15205c11b823c8107
Built: Wed Feb 23 20:34:57 2022
OS/Arch: linux/amd64
Server: Podman Engine
Version: 4.0.1
API Version: 4.0.1
Go Version: go1.16.14
Built: Fri Feb 25 18:05:11 2022
OS/Arch: linux/amd64
$ podman-remote machine ssh rpm -q podman
Warning: Permanently added '[localhost]:45253' (ECDSA) to the list of known hosts.
podman-4.0.1-1.fc35.x86_64 Waiting for Podman Desktop 4.1.0 is probably best, if there is something else with these early builds... ? So it's https://fedoraproject.org/wiki/Changes/Podman4.0 and then all the Fedora CoreOS stuff after that. |
Tried "rawhide", but it was still older.
|
it is So you could use Fedora or you could use Ubuntu, but like you say above it doesn't help...
Previously there were some smaller ISO images, but they won't be upgraded for podman4.
|
(This may be the wrong place for this, but it's at least related) |
Normally it is https://podman.io/getting-started/installation#building-from-scratch |
Since there are no Windows binaries, you need to build it from source instead https://podman.io/getting-started/installation#get-source-code Apparently there is no documentation, on how to build only the remote client... |
Things will get updated today for our 4.0.2 release. |
@baude That was SO easy!
|
The link in the |
There are static podman-remote binaries for v4.0.2 now. https://github.com/containers/podman/releases/tag/v4.0.2 |
Thanks a lot for the follow-up 😄 |
@gonzalocasas Try it now. |
yay! thanks, it works now! |
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
The static binaries are missing from the
Release
page, however it's mentioned in the Readme they should be available.Steps to reproduce the issue:
Describe the results you received:
Only source code is available to download.
Describe the results you expected:
The static binaries for Linux/MacOS/Windows should be listed
The text was updated successfully, but these errors were encountered: