Docker-Manifest

Derek Merck
derek_merck@brown.edu
Rhode Island Hospital and Brown University
Providence, RI

Create manifest files for multi-arch images from docker-compose service definitions.

Setup

$ pip install git+https://github.com/derekmerck/docker-manifest

Platform Dependencies: Docker Pip Dependencies: pyyaml, click

Usage

$ docker-manifest {-s service1,...} {-a amd64,...} namespace

docker-compose.yml services name keys should be formatted as "{service}-{arch}". For example:

services:
  my_service-amd64:
    image: my_image

This would register as a service definition with basename "my_service" and architecture "amd64". Architectures may be any one of amd64, arm32v7, or arm64v8.

$ docker-manifest -s my_service -a amd64 namespace would retag the output image my_image as namespace/my_service:latest-amd64 and link it to domain/my_service:tag on docker.io.

All images should be present in docker.io/my_namespace (not just locally) when the manifest is created, or the script will report failures and no manifest will be generated. Any locally available images will be retagged and pushed as part of this script when possible.

Notes

Acceptable architecture definitions are listed at https://raw.githubusercontent.com/docker-library/official-images/a7ad3081aa5f51584653073424217e461b72670a/bashbrew/go/vendor/src/github.com/docker-library/go-dockerlibrary/architecture/oci-platform.go

A good reference for manipulating docker manifest lists: https://lobradov.github.io/Building-docker-multiarch-images/#building-a-multi-arch-manifest

License

MIT