Docker build self destructed

[d-e-s-o]

Seems the Docker build self-destructed; e.g. https://github.com/d-e-s-o/cargo-http-registry/actions/runs/13312553321

 > [linux/arm64 builder 1/5] RUN apt-get update &&     apt-get install -y pkg-config libssl-dev &&     apt-get clean && rm -rf /var/lib/apt/lists/*:
42.60 Processing triggers for libc-bin (2.31-13+deb11u7) ...
42.75 qemu: uncaught target signal 11 (Segmentation fault) - core dumped
43.66 Segmentation fault (core dumped)
43.71 qemu: uncaught target signal 11 (Segmentation fault) - core dumped
44.49 Segmentation fault (core dumped)
44.50 dpkg: error processing package libc-bin (--configure):
44.50  installed libc-bin package post-installation script subprocess returned error exit status 139
44.59 Errors were encountered while processing:
44.59  libc-bin
44.80 E: Sub-process /usr/bin/dpkg returned an error code (1)

From a brief search, there seem to be plenty of occurrences of this in the wild:

• https://stackoverflow.com/questions/72778600/qemu-uncaught-target-signal-11-when-running-dpkg-configure-libc-bin
• https://stackoverflow.com/questions/72641113/qemu-uncaught-target-signal-11-segmentation-fault-core-dumped-while-using-b
• qemu: uncaught target signal 11 (Segmentation fault) - core dumped docker/buildx#1170
• qemu: uncaught target signal 11 (Segmentation fault) - core dumped docker/buildx#1169

FYI @marcoieni, in case you have the cycles to look at it.

[marcoieni]

Hi! Unfortunately I don't have cycles. In fact, docker build has been broken since forever in my own project 😂

[d-e-s-o]

@marcoieni I fixed the thing and it managed to stay green for not even a week. https://github.com/d-e-s-o/cargo-http-registry/actions/runs/13557290225 Going to remove it in two days. If you still have a use for it let me know and we can keep it in, but I'm afraid you'll need to find someone to maintain it.

[marcoieni]

I'm not using this anymore. I'm now using gitea in docker to create s private registry for my tests.
So you can drop docker support 👍