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

gator cli released binary not statically compiled #2825

Closed
csantanapr opened this issue Jun 11, 2023 · 0 comments · Fixed by #2840
Closed

gator cli released binary not statically compiled #2825

csantanapr opened this issue Jun 11, 2023 · 0 comments · Fixed by #2840
Labels
bug Something isn't working gator cmd

Comments

@csantanapr
Copy link

What steps did you take and what happened:

Downloaded the gator cli from github release page, when I run it on linux amd64 (ie amazonlinux2) I get errors
https://github.com/open-policy-agent/gatekeeper/releases/download/v3.12.0/gator-v3.12.0-linux-amd64.tar.gz

$ gator --version
./gator: /lib64/libc.so.6: version `GLIBC_2.32' not found (required by ./gator)
./gator: /lib64/libc.so.6: version `GLIBC_2.34' not found (required by ./gator)

Can we released on github releases the gator for linux the same as the one inside docker images?

What did you expect to happen:
For the gator CLI to not depend on OS libs

Anything else you would like to add:
I tried the gator CLI inside the docker images and this binaries are statically compiled with the option CGO_ENABLED=0
https://github.com/open-policy-agent/gatekeeper/blob/master/gator.Dockerfile#L16

This is linux/amd64 of gator 3.12.0 works

crane export openpolicyagent/gator@sha256:3ee4a41a51c524635bfa572b55f93cdb2b685f341acef62bb5168b8287e50961 gator.tar
@csantanapr csantanapr added the bug Something isn't working label Jun 11, 2023
@acpana acpana removed their assignment Jun 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working gator cmd
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants