Hi Greg, > > How do I get in contact with somebody who can fix the problem in > > Debian Buser and/ or the official Debian Buster arm32v7 Docker image? > > Looks a bit like <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923479> > to me.
Thanks a lot! Yes, this looks a lot like my problem. Also their workaround of running "c_rehash" works. :) The only difference I was able to spot is that my build process does not give the "qemu: Unsupported syscall: 382" error message. It stays completely silent. https://gitlab.com/toertel/docker-image-tls-https-broken/-/jobs/534935085#L317 317 Setting up ca-certificates (20190110) ... 318 Updating certificates in /etc/ssl/certs... 319 128 added, 0 removed; done. 320 Setting up libgssapi-krb5-2:armhf (1.17-3) ... 321 Setting up libcurl4:armhf (7.64.0-4+deb10u1) ... 322 Setting up curl (7.64.0-4+deb10u1) ... 323 Processing triggers for libc-bin (2.28-10) ... 324 Processing triggers for ca-certificates (20190110) ... 325 Updating certificates in /etc/ssl/certs... 326 0 added, 0 removed; done. 327 Running hooks in /etc/ca-certificates/update.d... 328 done. I implemented the workaround and it also works in GitLab CI. https://gitlab.com/toertel/docker-image-tls-https-broken/pipelines/142869786 Greetings, Mark
