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

.config/fastly/viceroy: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found #120

Closed
alameth opened this issue Jan 27, 2022 · 7 comments

Comments

@alameth
Copy link

alameth commented Jan 27, 2022

Version

Fastly CLI version 1.5.0 (0d495f7)
Built with go version go1.17.6 linux/amd64
Viceroy version: viceroy 0.2.9

What happened

$ fastly compute serve --addr "127.0.0.1":7880 --skip-build
Initializing...
Fetching latest Viceroy release...
Running local server...

/home/cgutekunst/.config/fastly/viceroy: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /home/cgutekunst/.config/fastly/viceroy)

ERROR: error during execution process:

/home/cgutekunst/.config/fastly/viceroy: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /home/cgutekunst/.config/fastly/viceroy).

If you believe this error is the result of a bug, please file an issue: https://github.com/fastly/cli/issues/new?labels=bug&template=bug_report.md

System lsb:

DISTRIB_ID=LinuxMint
DISTRIB_RELEASE=19.3
DISTRIB_CODENAME=tricia
DISTRIB_DESCRIPTION="Linux Mint 19.3 Tricia"

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.

@alameth
Copy link
Author

alameth commented Jan 27, 2022

Note I'm a Linux developer, running Mint 19.3 as my development environment. No docker here. :-)

@Integralist
Copy link
Contributor

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 viceroy binary, and for whatever reason the GLIBC dependency required by Viceroy is not available (or more likely not up-to-date) on your system.

An alternative to manually compiling Viceroy would be to update your GLIBC version.

@Integralist
Copy link
Contributor

The user @lyrixx also had the exact same issue and workaround.

@alameth
Copy link
Author

alameth commented Jan 27, 2022

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.

@Integralist
Copy link
Contributor

Integralist commented Jan 27, 2022

Upgrading the version of GLIBC on an LTS distro is hard, deliberately so; locally compiling viceroy was easy. :-)

Ah, yeah I guess my suggestion was a wee bit ...optimistic 😄

Thanks for the forward; this was just my best guess as to the correct team.

No problem 🙂

@mgattozzi
Copy link
Contributor

Since there's a workaround for this issue, I'm going to close this for now and have it be superseded by #174 so that we can avoid this issue in the future. Thanks for taking the time to open up the issue @alameth

@kanevbg
Copy link

kanevbg commented Dec 7, 2022

same issue on rhel 8

geekbeast pushed a commit to geekbeast/Viceroy that referenced this issue Jan 19, 2023
This should avoid pulling in breaking version of glibc until we address fastly#120.
acfoltzer pushed a commit that referenced this issue Jan 19, 2023
* 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]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants