Closed kpine closed 2 years ago
FYI, it builds fine if you switch the base image entirely to bullseye-slim and remove all of the repository modifications. Bullseye has the same QT 5.12.5 packages that sid does. Not sure if you want to go that route though, since it will update the dev toolchain as well (gcc 10, etc.).
I've switch to Ubuntu Focal as that has the required deps without having to use unstable repos
FYI - Bloody Issues with RPI images now. I'm looking at workarounds for this.. will advise when I get it building again .
Are you having trouble with breakpad?
Trying removing wget and replacing it with curl.
No. With this issue: https://github.com/moby/moby/issues/40734
Ahh, that does not sound good... Apparently, it only happens on native ARM hardware, https://github.com/osrf/multiarch-docker-image-generation/issues/38. I'm building the arm image on an amd64 host, which explains why I didn't encounter the same problem. Doubt it will actually run then.
Instead, I had an issue with fetch
failing because of wget and SSL certificates. Just swapping it for curl worked. Makes no sense.
Apparently, it only happens on native ARM hardware
Its actually a kernel version issue. The default kernel on rPI's is around 4.4 (from memory) but the Focal Release uses features from Kernel 5.5. It should gracefully fail and fall back. I could work around it and upgrade the kernel on the build hosts to 5.5, but I suspect it will still fail for users on the original 4.4 kernel.
So following those threads to see which way it gets fixed (either in the seccomp library, docker, or ubuntu focal)
4.19.97-v7+ #1294 SMP Thu Jan 30 13:15:58 GMT 2020 armv7l GNU/Linux
Maybe you're aware, but the image no longer builds due to what looks like updates to the unstable repository packages. Not sure if it's just a transient issue, if there is a workaround, or if they are now incompatible.