Oh, that’s neat!
I was trying to fix it, following along the lines of maybe the original bug report for Arch. But that got closed while it didn’t fix the underlying “Arch is broken when used in Docker” issue. Not keen on using patched versions of libraries, but will check how does it work for you, let’s see what we can learn. Thanks for sharing!

OK. I fixed my image by adding a patched glibc for the CircleCI infrastructure.

https://github.com/dmp1ce/archlinux-makepkg-docker

Annoying! I guess it is a glibc issue running on an old kernel on CircleCI servers.

https://stackoverflow.com/questions/66154574/archlinux-docker-ci-failed-to-initialise-alpm-library-returned-a-non-zero-cod

I’m again looking at your work on Github and Docker Hub to fix an issue I am having. I am getting the error “error: failed to initialize alpm library” from CircleCI when I use your “imrehg/archlinux-makepkg” image.

When I use my image “dmp1ce/archlinux-yay” I get “unable to CreateHandle: could not find or read directory”.

I’m really not sure why. Do you think it is a CircleCI issue?

Great job! You are maintaining quite a few packages! The no-submodule setup is cool too, indeed it’s optional, though I wonder when the tests are run, since package update doesn’t result in new code thus testing. Do you manually trigger tests or use scheduled builds? Actually, based this idea, just set up a nightly schedule for my AUR builds, that should be a good improvement to catch broken packages earlier. Thanks for the feedback, and let me know if you have any further ideas! :D