DevConf.CZ 2020

When you build a container image, you're usually building it for one OS, for one architecture. But your container image is awesome, which is why you pushed it to a container registry, so why make not make it easier for people to run it on other architectures? In this session, we'll look at different ways to build images for different architectures. We'll look at ways that people try to store the "same" image built for different architectures in a container registry, both by using conventions for naming images, and by using the standards-friendly method: manifest lists and image indexes. We'll build an image multiple times using buildah and/or podman, each time for a different architecture, push them all to a registry, and then demonstrate running it on machines of different architectures.