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
{{ message }}
This repository has been archived by the owner on Dec 18, 2024. It is now read-only.
In the requirements.txt file for kuksa-viss-client we state that we shall use grpcio ~= 1.46.0 and grpcio-tools ~= 1.46.0 but when using alpine (like in docker file) it seems that we need to build them from scratch if they are not cached, which can take > 45 minutes, like in this build
For many other Dockerfiles we use something else than Alpine and that is an alternative - but then we end up with a bigger container (as more junk included)
It seems that the wheel for grpcio/grpcio-tools is not complete - there are "hidden dependencies" to e.g. linux-headers and/or g++ needed if you need to build it yourself (as needed for arm with Alpine). I.e. you must install certain items by apk or pip before installing grpcio, see e.g. Upgrade docker build environment for gps2val eclipse-kuksa/kuksa.val.feeders#24.
The text was updated successfully, but these errors were encountered:
In the requirements.txt file for kuksa-viss-client we state that we shall use grpcio ~= 1.46.0 and grpcio-tools ~= 1.46.0 but when using alpine (like in docker file) it seems that we need to build them from scratch if they are not cached, which can take > 45 minutes, like in this build
I assume this is because e.g. https://pypi.org/project/grpcio-tools/1.46.5/#files does not have pre-built wheel for musllinux_1_1_aarch64 which is required when using Alpine.
Other observations:
413 request entity too large
while pushing an image replicatedhq/ttl.sh#104, see also Push to harbor fails with "413 Request Entity Too Large" docker/build-push-action#634The text was updated successfully, but these errors were encountered: