Previously, it was necessary to either docker pull ibmcom/ibmnode, docker pull ppc64le/ibmnode, or docker pull s390x/ibmnode depending on your architecture. Now, you can just do:

docker pull ibmcom/ibmnode

from a terminal, or in a Dockerfile:

FROM ibmcom/ibmnode

 

Multi-arch images, also named a ‘manifest list’ or ‘fat manifest’, allow you to group multiple images together. In the case of the IBK SDK for Node.js, the three different available architectures are grouped (amd64, ppc64le, and s390x). When you do a docker pull on the manifest list, the docker engine will determine which image to pull based on the OS and architecture the user was running on.

This is the manifest.yml we use for ibmcom/ibmnode.

image: ibmcom/ibmnode:{{VERSION}}
manifests:
  -
    image: ibmcom/ibmnode-amd64:{{VERSION}}
    platform:
      os: linux
      architecture: amd64
  -
    image: ibmcom/ibmnode-ppc64le:{{VERSION}}
    platform:
      os: linux
      architecture: ppc64le
  -
    image: ibmcom/ibmnode-s390x:{{VERSION}}
    platform:
      os: linux
      architecture: s390x

 

See https://developer.ibm.com/linuxonpower/2017/07/27/create-multi-architecture-docker-image/ for more information on multi-architecture Docker images.

Join The Discussion

Your email address will not be published. Required fields are marked *