-
Notifications
You must be signed in to change notification settings - Fork 534
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
Unable to Install Syft #1523
Comments
Seems like github may have changed the endpoint format? I turned trace level debugging on to find the curl command, and see:
I'm guessing that this used to return json instead of html. |
Hi @nkreiger I've just tried this out again for macOS and Linux and it seems to be working fine for me at this point, could you retry? NOTE I also saw a failure yesterday where https://github.com/anchore/grype/releases/download/v0.56.0/grype_0.56.0_linux_arm64.deb was returning 403 for some reason, but seems to be fine now. Similar to Grype, as @jdolitsky noted, it might be good to add a fallback to the API call here: https://api.github.com/repos/{org}/{repo}/releases/latest |
I would agree with the benefits of a fallback, as long as it doesn't become the only option. Sadly, the API requires a GitHub token even for public repositories. The default GitHub token provided in GitHub Actions doesn't work for this purpose, so repositories might have to use a PAT/application token. This might not be feasible for public repositories and would pose a security risk for something that should be public. |
I finally got around to trying this, and |
GitHub reverted the change, and I am able to use the install.sh script again. |
We'll close this one out but if GitHub makes any more changes we will definitely follow up. Thanks! |
Please provide a set of steps on how to reproduce the issue
Starting a few hours ago, it was noticed that installation of Syft is no longer working with the install.sh script.
What happened:
What you expected to happen:
No errors
Anything else we need to know?:
Environment:
syft version
:cat /etc/os-release
or similar): 22.04.1 LTS (Jammy Jellyfish)The text was updated successfully, but these errors were encountered: