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:
I hereby claim:
To claim this, I am signing this object:
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.
name:tag
manifest will need to contain the proper information for access/retrieval of multiple architectures
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 imagename:tag
manifests will have information forpackage main | |
import ( | |
"fmt" | |
"flag" | |
"regexp" | |
) | |
var ( | |
fullID = regexp.MustCompile(`^[0-9a-fA-F]{64}$`) |