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

protostar issue in our dev container #270

Closed
loothero opened this issue Dec 30, 2022 · 0 comments
Closed

protostar issue in our dev container #270

loothero opened this issue Dec 30, 2022 · 0 comments

Comments

@loothero
Copy link
Contributor

protostar appears to have introduced a dependency issue in v0.9.0 (also present in v0.9.1) which is documented here: [GLIBC_2.35 not found on Debian](software-mansion/protostar#1293)

Since our Dockerfile is configured to install latest protostar any newly built containers are likely to encounter this (until protostar fixes the issue)

The simple solution is to temporarily modify Dockerfile to target v0.8.1

kasperski95 added a commit to software-mansion/protostar that referenced this issue Jan 17, 2023
Use Ubuntu 20.04 to build binaries. [Protostar
v0.8.1](BibliothecaDAO/realms-contracts#270)
doesn't have this problem. [Recently, `ubuntu-latest` was updated to use
Ubuntu 22.04.](actions/runner-images#6399)


> You're better off finding a Python built with a lower glibc
requirement which in practice means building on an old version of Linux
or an old docker image.

pyinstaller/pyinstaller#5669

Probably Fixes #1293
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

2 participants