vbatts/registry
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity
registry/docs/spec/deprecated-schema-v1.md
Adrian Plata a3c027e626
Adding deprecated schema instructions 
Signed-off-by: Adrian Plata <adrian.plata@docker.com>
(cherry picked from commit 07a50201c9)
Signed-off-by: Derek McGowan <derek@mcgstyle.net>
2019-09-03 11:56:53 -07:00

2 KiB
Raw Blame History

title description keywords
Update deprecated schema image manifest version 2, v1 images Update deprecated schema v1 iamges registry, on-prem, images, tags, repository, distribution, api, advanced, manifest

Image manifest version 2, schema 1

With the release of image manifest version 2, schema 2, image manifest version 2, schema 1 has been deprecated. This could lead to compatibility and vulnerability issues in images that haven't been updated to image manifest version 2, schema 2.

This page contains information on how to update from image manifest version 2, schema 1. However, these instructions will not ensure your new image will run successfully. There may be several other issues to troubleshoot that are associated with the deprecated image manifest that will block your image from running succesfully. A list of possible methods to help update your image is also included below.

Update to image manifest version 2, schema 2

One way to upgrade an image from image manifest version 2, schema 1 to schema 2 is to docker pull the image and then docker push the image with a current version of Docker. Doing so will automatically convert the image to use the latest image manifest specification.

Converting an image to image manifest version 2, schema 2 converts the manifest format, but does not update the contents within the image. Images using manifest version 2, schema 1 may contain unpatched vulnerabilities. We recommend looking for an alternative image or rebuilding it.

Update FROM statement

You can rebuild the image by updating the FROM statement in your Dockerfile. If your image manifest is out-of-date, there is a chance the image pulled from your FROM statement in your Dockerfile is also out-of-date. See the Dockerfile reference and the Dockerfile best practices guide for more information on how to update the FROM statement in your Dockerfile.