Change manifest format on ECR images

[arunasank]

Ref: #97 (comment)

When you push and pull images to and from Amazon ECR, your container engine client (for example, Docker) communicates with the registry to agree on a manifest format that is understood by the client and the registry to use for the image.

When you push an image to Amazon ECR with Docker version 1.9 or older, the image manifest format is stored as Docker Image Manifest V2 Schema 1. When you push an image to Amazon ECR with Docker version 1.10 or newer, the image manifest format is stored as Docker Image Manifest V2 Schema 2.

When you pull an image from Amazon ECR by tag, Amazon ECR returns the image manifest format that is stored in the repository, but only if that format is understood by the client. If the stored image manifest format is not understood by the client (for example, if a Docker 1.9 client requests an image manifest that is stored as Docker Image Manifest V2 Schema 2), Amazon ECR converts the image manifest into a format that is understood by the client (in this case, Docker Image Manifest V2 Schema 1).

Next actions

• Update Docker version on ecs-conex
• Set up a stack to pull and re-push existing images on the ECR - this will be a one time task for existing images.

cc/ @mapbox/platform

[arunasank]

• Update Docker version on ecs-conex

Done in #16 and 87490a4. So, guess there are a mix of images in the old and new formats on the ECR.

• Set up a stack to pull and re-push existing images on the ECR - this will be a one time task for existing images.

We should do this for all images created on or before 17th Jan, 2017.

Update:

I rechecked the schema version in the manifest file, after realising that the image I referenced was created after the Docker upgrade to 1.12*, and I see

{
   "schemaVersion": 2
......
......
......
}

Going to follow up with AWS Support.