> ```
> $ docker run --rm -t arm64v8/fedora:30 uname -m
standard_init_linux.go:207: exec user process caused "no such file or
directory"
> $ docker run --rm --privileged multiarch/qemu-user-static:register --reset
> $ docker run --rm -t quay.io/junaruga/multiarch-fedora:30-aarch64 uname -m
> aarch64
Recently our multiarch project released a new feature to enable to run
a standard multi-architecture containers on x86_64, without
multiarch/* container that was needed before, not depending on host OS
environment.
That means below workflow works
```
$ uname -m
x86_64
$ docker run --rm -t arm64v8/ubuntu uname -m
standard_init_linux.go:211: exec user process caused "exec format error"
$ docker run --rm --privileged multiarch/qemu-user-static --reset -p yes
$ docker run --rm -t arm64v8/fedora:30 uname -m
aarch64
```
Is it fine to advertise my talk at Flock 2019 this Friday here? :)
Title: Let's add Fedora multiarch containers to your CI.
https://flock2019.sched.com/event/SJLx/lets-add-fedora-multiarch-containe...
* When: Friday August 9, 2019 10:30 - 10:55
* Where: the room Panorama (140m² / 40 people), The Danubius Hotel
HELIA in Budapest, Hungary, at Flock Budapest 2019
= Table of contents = (it might be changed a little bit later)
* Fedora and Upstream - Past and Present
* CPU Architecture Kinds
* Tools for multiarch - Today's topics
* QEMU and binfmt_misc - on News
* 5 steps - to add Fedora multiarch to upstream CI
* 1. qemu-$arch-static - An interpreter
* 2. binfmt_misc - A kernel feature for binary format
* 3. qemu-user-static RPM on Fedora
* 4. qemu-user-static RPM and container
* 5. multiarch/qemu-user-static image and CI
* Note A: ARM supported CI services
* Note B: A Dockerfile to multi-arch images
docker buildx, docker/(podman) build --platform
Please come!