You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
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
The text was updated successfully, but these errors were encountered: