Rjerk

吼啊

I build for arm64 version for my own usage: https://github.com/Rjerk/alpine-pkg-glibc/releases/tag/2.30-r0-arm64

I build for arm64 version for my own usage: https://github.com/Rjerk/alpine-pkg-glibc/releases/tag/2.30-r0-arm64

> UNTRUSTED signature > > how can I fix this problem? `apk add --allow-untrusted` should work. > --allow-untrusted Install packages with untrusted signature or no signature

> ```dockerfile > apk add --no-cache \ > "$ALPINE_GLIBC_BASE_PACKAGE_FILENAME" \ > "$ALPINE_GLIBC_BIN_PACKAGE_FILENAME" \ > "$ALPINE_GLIBC_I18N_PACKAGE_FILENAME" && \ > ``` add `--allow-untrusted` here I guess

> @Rjerk you mean you built your own Docker image? I'm trying to replicate the build of this container on a rpi4 but it's failing with a message like `/usr/glibc-compat/sbin/ldconfig:...

I have the same error, do u resolve it? @lemont79

The alpine source may not stable I guess. workaround: I remove py2-yaml from `apk add py2-yaml` and add these lines (arm64) ``` wget http://dl-8.alpinelinux.org/alpine/v3.8/main/aarch64/py2-yaml-3.12-r1.apk && \ apk add --allow-untrusted py2-yaml-3.12-r1.apk...

> I can't find package which contains libc.musl-aarch64.so.1 lib. try: ``` apk add musl ```

> This is alpine version confilct error > fix > `FROM alpine:latest as py-ea` ->`FROM alpine:3.8 as py-ea` it works : )