-
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
Static binary build fails #13259
Comments
nix log:
|
Upstream does not controll how we build on downstream platforms. I don't see this as a Podman issue. |
Static compilation is listed as valid installation method in official Podman docs |
Sure but it is up to community to figure out why it is broken on different distributions. Upstream maintainers only work on a select few distros. |
The podman project only supports static builds of the client (podman-remote), not of the server (podman) https://github.com/containers/podman/releases/latest You can find some workarounds for the failing Nix build (sandbox issue with Go) in: #8788 (comment)
https://podman.io/getting-started/installation#ubuntu EDIT: the original nix bug from 2019 is still open |
AFAIK The static nix build in the podman repo is currently unmaintained. We removed the CI job since nobody fixed the failures. I think you have better luck with the official podman nix package: https://search.nixos.org/packages?channel=21.11&show=podman&from=0&size=50&sort=relevance&type=packages&query=podman |
@Luap99 Does the official nix package produce static binaries as well? |
nix only builds static binaries AFAIK |
A friendly reminder that this issue had no activity for 30 days. |
Since this is not supported upstream I am closing. |
If we do not want to support this and there is no one from the community we should remove it. |
I agree, I also think a static Podman makes little sence, since Podman relies on so many other programs to be able to run properly. It is not a standalone application. |
The other container runtimes provide an all-in-one tarball, it is not fully static but it does include e.g. Example: nerdctl-full.tgz |
Well if someone in community is interested in maintaining that then they are welcome to it. But if it is just going to be a source os issues, with mismatched versions, then it is more of a pain. Running a container image from a distribution is a simpler solution if people want to try newer versions of XYZ container engine. |
Yes, probably best to remove the old nix files from the git repository if they are not working (or being tested) anyway. |
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
Steps to reproduce the issue:
curl -L https://nixos.org/nix/install | sh
git clone https://github.com/containers/podman.git && cd podman
nix --experimental-features nix-command build -f nix/
Describe the results you received:
Following error message is displayed:
Describe the results you expected:
Working podman binary
Additional information you deem important (e.g. issue happens only occasionally):
Additional environment details (AWS, VirtualBox, physical, etc.):
Ubuntu 20.04 server, baremetal
The text was updated successfully, but these errors were encountered: