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.

Sign up for GitHub

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

Jump to bottom

Document new binary requirements #256

Closed
afbjorklund opened this issue Aug 9, 2023 · 3 comments · Fixed by #260
Closed

Document new binary requirements #256

afbjorklund opened this issue Aug 9, 2023 · 3 comments · Fixed by #260

Comments

@afbjorklund
Copy link

afbjorklund commented Aug 9, 2023 •
edited
Loading

The old gvproxy 0.6.2 also ran on Ubuntu 20.04 (glibc 2.31)

But the new gvproxy 0.7.0 requires Ubuntu 22.04 (glibc 2.35)

/usr/local/libexec/podman/gvproxy: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by /usr/local/libexec/podman/gvproxy)
/usr/local/libexec/podman/gvproxy: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /usr/local/libexec/podman/gvproxy)

The arch variants seem to be missing, as well:

gvproxy-linux-amd64
gvproxy-linux-arm64

Building from source code instead worked...
@cfergeau
Copy link
Collaborator

The arch variants seem to be missing, as well:

gvproxy-linux-amd64
gvproxy-linux-arm64

I don't think there ever were linux-arm64 builds with releases (0.6.2 did not have it), but I can add one in the future.

@cfergeau
Copy link
Collaborator

The old gvproxy 0.6.2 also ran on Ubuntu 20.04 (glibc 2.31)
But the new gvproxy 0.7.0 requires Ubuntu 22.04 (glibc 2.35)

The binaries are built in github actions on an ubuntu-latest image, using ubuntu-20.04 instead/in addition to -latest should help.

cfergeau added a commit to cfergeau/gvisor-tap-vsock that referenced this issue Aug 16, 2023
@cfergeau
ghactions: Build on ubuntu 20.04
5843b3a 
We use the binaries built on github actions for releases, and binaries
built on newer ubuntus/libc may not work on older ubuntus:
containers#256

This commit switches from an ubuntu-latest image to ubuntu-20.04

Signed-off-by: Christophe Fergeau <cfergeau@redhat.com>
cfergeau added a commit to cfergeau/gvisor-tap-vsock that referenced this issue Aug 16, 2023
@cfergeau
build: Build arm64 linux binary
fb43b49 
This was requested in containers#256

Signed-off-by: Christophe Fergeau <cfergeau@redhat.com>
@afbjorklund
Copy link
Author

Thanks!

cfergeau added a commit to cfergeau/gvisor-tap-vsock that referenced this issue Aug 17, 2023
@cfergeau
build: Build arm64 linux binary
c3dc0f0 
This was requested in containers#256

The arm64 binary is named gvproxy-linux-arm64, and the amd64 binary is
renamed to gvproxy-linux-amd64 for consistency.

Signed-off-by: Christophe Fergeau <cfergeau@redhat.com>
@cfergeau cfergeau mentioned this issue Aug 17, 2023
Merged
cfergeau added a commit to cfergeau/gvisor-tap-vsock that referenced this issue Aug 21, 2023
@cfergeau
ghactions: Build on ubuntu 20.04
428c400 
We use the binaries built on github actions for releases, and binaries
built on newer ubuntus/libc may not work on older ubuntus:
containers#256

This commit switches from an ubuntu-latest image to ubuntu-20.04

Signed-off-by: Christophe Fergeau <cfergeau@redhat.com>
cfergeau added a commit to cfergeau/gvisor-tap-vsock that referenced this issue Aug 21, 2023
@cfergeau
build: Build arm64 linux binary
70135b3 
This was requested in containers#256

The arm64 binary is named gvproxy-linux-arm64, and the amd64 binary is
renamed to gvproxy-linux-amd64 for consistency.

Signed-off-by: Christophe Fergeau <cfergeau@redhat.com>
cfergeau added a commit to cfergeau/gvisor-tap-vsock that referenced this issue Sep 6, 2023
@cfergeau
ghactions: Add comment explaining why we stay on ubuntu-20.04
33b6fb2 
It's used on purpose, see commit 428c400 and
containers#256
cfergeau added a commit to cfergeau/gvisor-tap-vsock that referenced this issue Sep 11, 2023
@cfergeau
ghactions: Add comment explaining why we stay on ubuntu-20.04
8ca934a 
It's used on purpose, see commit 428c400 and
containers#256
cfergeau added a commit to cfergeau/gvisor-tap-vsock that referenced this issue Sep 21, 2023
@cfergeau
ghactions: Add comment explaining why we stay on ubuntu-20.04
437829f 
It's used on purpose, see commit 428c400 and
containers#256
cfergeau added a commit to cfergeau/gvisor-tap-vsock that referenced this issue Sep 21, 2023
@cfergeau
ghactions: Add comment explaining why we stay on ubuntu-20.04
b1731b1 
It's used on purpose, see commit 428c400 and
containers#256

Signed-off-by: Christophe Fergeau <cfergeau@redhat.com>
@gbraad gbraad mentioned this issue Jan 10, 2025
Merged
cfergeau added a commit to cfergeau/gvisor-tap-vsock that referenced this issue Jan 10, 2025
@cfergeau
Revert "Update ubuntu runner to 'ubuntu-24.04'"
f88fbdf 
This reverts commit 2959505.
We prefer to stick with older ubuntu releases for building because of
containers#256
The issue with qemu with ubuntu 20.04 was fixed with
containers@fe7285a8a6a

Ubuntu 20.04 will be EOL'ed in April and the runner images will also go
away so we'll need to revisit this:
actions/runner-images#11101

Some options are to switch to Ubuntu 22.04 for our builds, or to look
into having pure go builds or statically linked builds, ...

Signed-off-by: Christophe Fergeau <cfergeau@redhat.com>
@cfergeau cfergeau mentioned this issue Jan 10, 2025
Merged
cfergeau added a commit to cfergeau/gvisor-tap-vsock that referenced this issue Jan 10, 2025
@cfergeau
Revert "Update ubuntu runner to 'ubuntu-24.04'"
59ebb1c 
This reverts commit 2959505.
We prefer to stick with older ubuntu releases for building because of
containers#256
The issue with qemu with ubuntu 20.04 was fixed with
containers@fe7285a8a6a

Ubuntu 20.04 will be EOL'ed in April and the runner images will also go
away so we'll need to revisit this:
actions/runner-images#11101

Some options are to switch to Ubuntu 22.04 for our builds, or to look
into having pure go builds or statically linked builds, ...

Signed-off-by: Christophe Fergeau <cfergeau@redhat.com>
cfergeau added a commit that referenced this issue Jan 20, 2025
@cfergeau
Revert "Update ubuntu runner to 'ubuntu-24.04'"
31b50f3 
This reverts commit 2959505.
We prefer to stick with older ubuntu releases for building because of
#256
The issue with qemu with ubuntu 20.04 was fixed with
fe7285a8a6a

Ubuntu 20.04 will be EOL'ed in April and the runner images will also go
away so we'll need to revisit this:
actions/runner-images#11101

Some options are to switch to Ubuntu 22.04 for our builds, or to look
into having pure go builds or statically linked builds, ...

Signed-off-by: Christophe Fergeau <cfergeau@redhat.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Misc build changes cfergeau/gvisor-tap-vsock
2 participants
@cfergeau @afbjorklund