Skip to content

Add platform specification to Docker commands, fix build command #217

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Alestrix wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Add platform specification to Docker commands, fix build command #217

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 11 additions & 10 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,8 @@ Here are examples with Docker [<sup>3</sup>](#ref-3).
$ uname -m
x86_64

$ docker run --rm -t arm64v8/ubuntu uname -m
# Need to provide platform on first pull
$ docker run --rm --platform arm64 -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
Expand All @@ -25,25 +26,25 @@ aarch64
It works on many architectures and OS container images.

```
$ docker run --rm -t arm32v6/alpine uname -m
$ docker run --rm --platform arm32 -t arm32v6/alpine uname -m
armv7l

$ docker run --rm -t ppc64le/debian uname -m
$ docker run --rm --platform ppc64le -t ppc64le/debian uname -m
ppc64le

$ docker run --rm -t s390x/ubuntu uname -m
$ docker run --rm --platform s390x -t s390x/ubuntu uname -m
s390x

$ docker run --rm -t arm64v8/fedora uname -m
$ docker run --rm --platform arm64 -t arm64v8/fedora uname -m
aarch64

$ docker run --rm -t arm32v7/centos uname -m
$ docker run --rm --platform arm -t arm32v7/centos uname -m
armv7l

$ docker run --rm -t ppc64le/busybox uname -m
$ docker run --rm --platform ppc64le -t ppc64le/busybox uname -m
ppc64le

$ docker run --rm -t i386/ubuntu uname -m
$ docker run --rm --platform i386 -t i386/ubuntu uname -m
x86_64
```

Expand All @@ -52,7 +53,7 @@ Podman [<sup>4</sup>](#ref-4) also works.
```
$ sudo podman run --rm --privileged multiarch/qemu-user-static --reset -p yes

$ podman run --rm -t arm64v8/fedora uname -m
$ podman run --rm --platform=arm64 -t arm64v8/fedora uname -m
aarch64
```

Expand Down Expand Up @@ -175,7 +176,7 @@ Because when the binfmt_misc entry is registered without `-p` option, the interp
```
$ docker run --rm --privileged multiarch/qemu-user-static:register --reset

$ docker build --rm -t "test/integration/ubuntu" -<<EOF
$ docker build --rm -t "test/integration/ubuntu" -f - . <<EOF
FROM multiarch/qemu-user-static:x86_64-aarch64 as qemu
FROM arm64v8/ubuntu
COPY --from=qemu /usr/bin/qemu-aarch64-static /usr/bin
Expand Down