Docker Community Forums

Share and learn in the Docker community.

Error: no matching manifest for linux/s390x in the manifest list entries. linux/s390x and s390x architecture mismatch?

I’m playing first day with docker on more rare architecture (LinuxOne, RHEL on s390x) and I suspect that there is a mismatch between architecture string what the docker uses and what is written in manifestos in docker hub.

Now, when I’m looking at (easiest to find link) I see the “IBM Z” tag, combo box with no effect has “Linux - IBM Z ( latest )” option in it and it suggests that simply running docker pull node I’ll get a node container. Here is what happens:

$ docker --debug pull node
Using default tag: latest
latest: Pulling from library/node
no matching manifest for linux/s390x in the manifest list entries

If I look here https://hub.docker.com/r/s390x/node/ it suggests to run docker pull s390x/node and it works:

$ docker pull s390x/node
Using default tag: latest
latest: Pulling from s390x/node
cc8faf537ff8: Pull complete
9816eeae17f4: Pull complete
13a7344ca59d: Pull complete
e6a933209363: Pull complete
6abb293160bb: Pull complete
faf135d701f8: Pull complete
80741dcaea5e: Pull complete
6a3670435671: Pull complete
e9082185059e: Pull complete
Digest: sha256:0385b823bd387f1d7084bcf28e5f86666c026fed635e3c35684ef227570242bc
Status: Downloaded newer image for s390x/node:latest
docker.io/s390x/node:latest

My question is why I can’t simply run container node, but s390x/node instead? Why do I get “no matching manifest for linux/s390x in the manifest list entries” message?

More info on question (to overcome "only 2 links per question limit):