Hi everyone, On 18.03.22 at 17:47 Johannes Kastl wrote:
On 11.03.22 at 08:49 Johannes Kastl wrote:
The buildah call still does not work, but now I get another error message...
$ buildah bud --arch arm64 . STEP 1/2: FROM registry.access.redhat.com/ubi8:latest STEP 2/2: RUN uname -a error building at STEP "RUN uname -a": error while running runtime: exit status 255 ERRO[0003] exit status 255
I opened both a bugzilla for qemu as well as an issue with buildah upstream. More information on the binfmt thingy would be nice, and a check to see if it is set up properly would be even better.
https://bugzilla.opensuse.org/show_bug.cgi?id=1197298 https://github.com/containers/buildah/issues/3827
The result from the buildah bugreport is that apparently the binaries in the qemu-linux-user package are dynamically linked and thus not working in this scenario. (I cannot verify if that is true, but I believe it is.) An alternative would be to run a privileged container that then registers the binaries: podman run --rm --privileged docker.io/multiarch/qemu-user-static --reset --persistent yes I just tested this on a Tumbleweed VM and could successfully "build" the examples from the podman example. Question to the ones with more knowledge on qemu and related packages: Could we have a subpackage of qemu containing statically linked binaries for this usecase? Or change the existing package to contain statically linked binaries? Or is that already existing in OBS but not in Tumbleweed? Or it is but I did not find it? I don't like the idea of having to run a container with root permissions on each boot of the OS just to register those binfmt thingies. Thanks in advance and have a nice weekend! Johannes -- Johannes Kastl Linux Consultant & Trainer Tel.: +49 (0) 151 2372 5802 Mail: kastl@b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg http://www.b1-systems.de GF: Ralph Dehner Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537