They produce outputs close to the original commands and support options of docker container ls and docker image ls. To list the architecture of the containers, you can use the following "quick" query: for i in `docker ps -format "' |Ĭolumn -table -table-columns "REPOSITORY,TAG,IMAGE ID,SIZE,ARCH" -o ' ' -s $'\t' The reason for this is that bitfmt (which is the underlying mechanism sitting inside the linux kernel) will always try to recognize the architecture from the magic numbers of the elf and will start the the emulation if the magic number is recognized. It should be noted that the "Architecture" flag on the image will not prevent a single process inside the image, which is compiled for a different architecture than the flagged one to run. Any of the containers that will run the image will be associated (trough the image) with this flag. The targeted architecture is determined from the "Architecture" flag on the image which was set when the image was build. Though the recognizing of the architecture is more related to the process, there is still information about the targeted architecture of the docker image. The mechanism for emulation is using the information in the elf to recognize the architecture for which the process is build, and if the architecture of the binary differs from the architecture of the CPU, it starts the qemu emulation.
This is true also for Docker running on amd64 CPU, when the image is build for arm64, and the whole mechanism is explained in this SO
0 kommentar(er)
