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

v4.0.0 missing static binaries in Release page #13298

Closed
nunix opened this issue Feb 20, 2022 · 31 comments
Closed

v4.0.0 missing static binaries in Release page #13298

nunix opened this issue Feb 20, 2022 · 31 comments
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

@nunix
Copy link

nunix commented Feb 20, 2022

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:

  1. Only 2 assets are on the Release page (instead of 7 for 3.4.4)

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

@openshift-ci openshift-ci bot added the kind/bug Categorizes issue or PR as related to a bug. label Feb 20, 2022
@mheon
Copy link
Member

mheon commented Feb 20, 2022

I was told not to build them yet by @baude - I'll defer explanation as to why to him

@nunix
Copy link
Author

nunix commented Feb 20, 2022

@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)

@baude
Copy link
Member

baude commented Feb 20, 2022

@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.

@nunix
Copy link
Author

nunix commented Feb 20, 2022

@baude thank you for the detailed answer, totally understandable. I will compile the msi as I did for the RC4 as I want to showcase the new podman machine with the WSL2 backend.

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 😄

@afbjorklund
Copy link
Contributor

afbjorklund commented Feb 21, 2022

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

Client:       Podman Engine
Version:      4.0.0-dev
API Version:  4.0.0-dev
Server:       Podman Engine
Version:      4.0.0-rc5
API Version:  4.0.0-rc5

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")

Fedora CoreOS 35.20220216.dev.0

podman-4.0.0-0.7.rc5.fc35.x86_64

@mheon
Copy link
Member

mheon commented Feb 21, 2022

I think the server is still waiting for packages to go stable so we can update the VM images. The client is concerning, though.

@afbjorklund
Copy link
Contributor

afbjorklund commented Feb 21, 2022

I think it accidentally tagged the commit before the version bump...

@mheon
Copy link
Member

mheon commented Feb 21, 2022

Uh-oh. You are entirely correct.

I can recreate the tag from the correct commit, but that could confuse things?

@afbjorklund
Copy link
Contributor

It happens...

I guess it will be fixed in 4.0.1, and it doesn't have much to do with the static podman-remote binaries.

@afbjorklund
Copy link
Contributor

@mheon this also meant that Podman 4.0.0 still uses the 3.3.1 API (not 4.0.0 API)

@mheon
Copy link
Member

mheon commented Feb 22, 2022

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).

@gonzalocasas
Copy link

Perhaps it is obvious, but is not only in the readme. The download link for Windows on the Getting started page of the website also ends up in 404.

@afbjorklund
Copy link
Contributor

afbjorklund commented Feb 26, 2022

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)

@fjorgemota
Copy link

I don't think a new issue for "v4.0.1 is also missing static binaries in Release page" would help ?

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..

@afbjorklund
Copy link
Contributor

afbjorklund commented Feb 26, 2022

I think static builds for podman-remote (client) were supposed to be there, but not for podman (server).

@fjorgemota
Copy link

I think static builds for podman-remote (client) were supposed to be there, but not for podman (server).

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.

@afbjorklund
Copy link
Contributor

afbjorklund commented Feb 26, 2022

I understand that it is some kind of weird side-track, but I did think that it was "released" as in "out there".

It (v4.0.1) seemed OK on Linux, downloaded fedora-coreos-35.20220225.dev.0-qemu.x86_64.qcow2.xz

$ 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.

@afbjorklund
Copy link
Contributor

afbjorklund commented Feb 27, 2022

Tried "rawhide", but it was still older.

podman-4.0.0-0.6.rc4.fc37.x86_64

@afbjorklund
Copy link
Contributor

afbjorklund commented Feb 27, 2022

the distro that's used on the virtual machine that podman-remote manages

it is podman machine that manages CoreOS, podman-remote can talk to any OS


So you could use Fedora or you could use Ubuntu, but like you say above it doesn't help...

  • podman.x86_64 3:3.4.4-1.fc35 updates

  • podman/impish 3.2.1+ds1-2ubuntu3 amd64

Previously there were some smaller ISO images, but they won't be upgraded for podman4.

  • podman.x86_64 2:1.8.0-4.fc30 updates

  • podman-3.2.3-r1 x86_64 {podman} (Apache-2.0) [installed]

@farfromunique
Copy link

(This may be the wrong place for this, but it's at least related)
How can I build the Podman-remote binary for windows? I'm not at all familiar with compiled-language software development...

@afbjorklund
Copy link
Contributor

How can I build the Podman-remote binary for windows?

Normally it is make podman-remote-windows, but please open a new issue if it doesn't work using the instructions

https://podman.io/getting-started/installation#building-from-scratch

@farfromunique
Copy link

Following that link (and searching for "Windows") tells me to install the latest remote client or read a blog post about how to install it for WSL. It says nothing about the make command.
It may be wise to update the documentation.
image

@afbjorklund
Copy link
Contributor

afbjorklund commented Mar 2, 2022

That assumes that there is a release, which might be true again for 4.1 or so ?

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...

@baude
Copy link
Member

baude commented Mar 2, 2022

Things will get updated today for our 4.0.2 release.

@farfromunique
Copy link

@baude That was SO easy!
For anyone who finds this later, here's what the instructions probably should be for v4.0.2 on Windows, with WSL2 backend:

download and run podman-v4.0.2.msi (it doesn't look like it does anything, but it does; just very fast!)
Powershell:
1) podman machine init (wait for it to be done. it'll tell you to run...)
2) podman machine start (wait ...)
3) podman run hello-world

@gonzalocasas
Copy link

@afbjorklund
Copy link
Contributor

There are static podman-remote binaries for v4.0.2 now.

https://github.com/containers/podman/releases/tag/v4.0.2

@nunix
Copy link
Author

nunix commented Mar 3, 2022

Thanks a lot for the follow-up 😄

@rhatdan rhatdan closed this as completed Mar 3, 2022
@gonzalocasas
Copy link

gonzalocasas commented Mar 3, 2022

sorry to insist, but the main entry point for most new people (on Windows) still returns an error when trying to download the binary:

image

@rhatdan
Copy link
Member

rhatdan commented Mar 3, 2022

@gonzalocasas Try it now.

@gonzalocasas
Copy link

yay! thanks, it works now!

@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 Sep 20, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 20, 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

8 participants