Skip to content

Instantly share code, notes, and snippets.

View estesp's full-sized avatar
💻
I work on containers. And review PRs.

Phil Estes estesp

💻
I work on containers. And review PRs.
View GitHub Profile

Keybase proof

I hereby claim:

  • I am estesp on github.
  • I am estesp (https://keybase.io/estesp) on keybase.
  • I have a public key whose fingerprint is 27F3 EA26 8A97 867E AF0B D05C 0F38 6284 C03A 1162

To claim this, I am signing this object:

@estesp
estesp / Multi-arch Implementation.md
Last active March 21, 2017 14:10
Multi-architecture support in content manifest scheme version 2

The new generic distributed content manifest format (schema version 2) [see distribution/distribution#62] is approaching final approval, and while some discussion has happened in-line, it seems reasonable to break out the various pieces that would be required to implement a multi-arch Docker image solution on top of the flexible manifest format being proposed.

As a starting point it is useful to discuss what the intended use case is for multi-architecture images in the Docker platform. The following requirements summarize the expected capabilities of the engine + registry + storage/retrieval format that is implemented.

Requirements

  • A specific repository name:tag manifest will need to contain the proper information for access/retrieval of multiple architectures
    • For example docker pull ubuntu:15.04 should have the capability on a POWER system to pull the POWER-specific image layers which comprise an Ubuntu 15.04 image
  • Not every name:tag manifests will have information for
@estesp
estesp / idmatch.go
Created September 18, 2014 19:21
proposal for name vs. ID lookup priority
package main
import (
"fmt"
"flag"
"regexp"
)
var (
fullID = regexp.MustCompile(`^[0-9a-fA-F]{64}$`)