Segfault on libc-bin

[ggjulio]

It seem there is a regression switching from master@sha256:f1c75c13ba55ac5414206cec87b284de4c573afa11553f4eebca451edae039ee to 10.1.3-60

The segfault occur on envoyproxy/envoy:v1.37-latest (ubuntu image), on other distro it seem to work fine.

[docker-bake] 48.06 Setting up libc-bin (2.35-0ubuntu3.13) ... 
[docker-bake] 49.83 qemu: uncaught target signal 11 (Segmentation fault) - core dumped 
[docker-bake] 49.90 Segmentation fault (core dumped) 
[docker-bake] 49.94 qemu: uncaught target signal 11 (Segmentation fault) - core dumped 
[docker-bake] 50.00 Segmentation fault (core dumped) 
[docker-bake] 50.03 dpkg: error processing package libc-bin (--configure): 
[docker-bake] 50.03  installed libc-bin package post-installation script subprocess returned error exit status 139 
[docker-bake] 50.60 Errors were encountered while processing: 
[docker-bake] 50.60  libc-bin 
[docker-bake] [WARNING] [stderr] 50.77 E: Sub-process /usr/bin/dpkg returned an error code (1) 

[ggjulio]

Not 100% sure if it's the root cause but it finally passed when disabling the buildkit cache.

[crazy-max]

Don't think BuildKit is the root cause but smth flaky with QEMU. If you can set ENV QEMU_STRACE=1 in your Dockerfile to have more info. Can you also try with crazymax/binfmt:v10.2.1 to check if #299 works?

[ggjulio]

For now I don't have the segv anymore but i'll write an update with traces if it occur again.
Thx !