-
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
BUG: podman-remote-static crash in ubuntu 20.04 (wsl) #13557
Comments
Initial thought: is the static build actually static? Anyone run |
If it matters, I built it on rawhide with go 1.18 (i think it was an rc back then). |
It is a known bug in Go, when linking statically with glibc Mentioned here: http://tbg.github.io/golang-static-linking-bug |
using the executable on a centos 9 stream, I see:
|
Ah, lovely. I love Go. |
@afbjorklund @mheon ummm, so do we need to build for each distro-release combination? |
This comment was marked as outdated.
This comment was marked as outdated.
I'm getting a ton of warnings, when building
Probably related to the change of Previously, it was set to |
Why did we do that? I don't know that podman-remote actually needs cgo. |
ab4c9a8 suggests there is a legitimate reason to want to do it, which is unfortunate |
It was done here: 319fcf5 $(SRCBINDIR)/podman-remote-static: $(SRCBINDIR) .gopathok $(SOURCES) go.mod go.sum
- CGO_ENABLED=0 \
- GOOS=$(GOOS) \
- $(GO) build \
+ $(GOCMD) build \
$(BUILDFLAGS) \
|
@lsm5 probably just delete podman-remote-static.tar.gz, similar to the other static build ? (the Nix one) Previously podman-remote was available in the podman deb.
|
@afbjorklund yes, I find building with musl a PITA too. I'm cool with removing podman-remote-static. @mheon @ashley-cui @baude @rhatdan wdyt? |
Why not just disable cgo, we clearly have users using it. |
@Luap99 do you mean something like:
Don't know if that's supposed to work or if musl has a separate set of variables. Without the CGO_CFLAGS, it isn't able to find That gives me:
|
Because you still have cgo enabled:
|
ah I see, that did give me a successful build. Let me test the binary on another env. Thanks! |
Resolves: containers#13557 [NO NEW TESTS NEEDED] Signed-off-by: Lokesh Mandvekar <lsm5@fedoraproject.org>
Resolves: containers#13557 [NO NEW TESTS NEEDED] Signed-off-by: Lokesh Mandvekar <lsm5@fedoraproject.org>
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
old version works fine
Steps to reproduce the issue:
download https://github.com/containers/podman/releases/download/v4.0.2/podman-remote-static.tar.gz
un-tar it
run it
Describe the results you received:
crash, see above
Describe the results you expected:
don't crash, show version
Additional information you deem important (e.g. issue happens only occasionally):
Output of
podman version
:not possible, see above but should be 4.0.2
Output of
podman info --debug
:not possible, see above
Package info (e.g. output of
rpm -q podman
orapt list podman
):direct download from github, see above
Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide? (https://github.com/containers/podman/blob/main/troubleshooting.md)
Yes
Additional environment details (AWS, VirtualBox, physical, etc.):
Ubuntu in Windows 11 WSL but did not work in Windows 10 also.
WSL
Ubuntu-20.04> reini@wsl:/Downloads$ lsb_release -aNo LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 20.04.4 LTS
Release: 20.04
Codename: focal
The text was updated successfully, but these errors were encountered: