-
Notifications
You must be signed in to change notification settings - Fork 38
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
.config/fastly/viceroy: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found #120
Comments
Note I'm a Linux developer, running Mint 19.3 as my development environment. No docker here. :-) |
Thanks @alameth for raising this issue, but I think this might be better passed over to the Viceroy team: https://github.com/fastly/viceroy to comment on as it's not a bug with the CLI. The CLI is downloading the linux/amd64 version of the An alternative to manually compiling Viceroy would be to update your GLIBC version. |
The user @lyrixx also had the exact same issue and workaround. |
Upgrading the version of GLIBC on an LTS distro is hard, deliberately so; locally compiling viceroy was easy. :-) Thanks for the forward; this was just my best guess as to the correct team. |
Ah, yeah I guess my suggestion was a wee bit ...optimistic 😄
No problem 🙂 |
same issue on rhel 8 |
This should avoid pulling in breaking version of glibc until we address fastly#120.
* Pin test and release runners to ubuntu-20.04 This should avoid pulling in breaking version of glibc until we address #120. * Also pin windows and mac. Co-authored-by: Matthew Tamayo <[email protected]>
Version
What happened
System lsb:
I'm guessing that the prebuilt (downloaded) version of Viceroy was built on Ubuntu 20; I'm on Mint 19.3, which is wrapper around Ubuntu 18.04 LTS.
WORKAROUND
Built viceroy from source and hard linked it from cargo/.bin to .config/fastly.
The text was updated successfully, but these errors were encountered: