Create deprecated-schema-v1.md

Signed-off-by: Adrian Plata <adrian.plata@docker.com>

smoothing content

Signed-off-by: Adrian Plata <adrian.plata@docker.com>

more information and link

Signed-off-by: Adrian Plata <adrian.plata@docker.com>

minor text changes

Signed-off-by: Adrian Plata <adrian.plata@docker.com>

added another link

Signed-off-by: Adrian Plata <adrian.plata@docker.com>

docs/spec/deprecated-schema-v1.md

@@ -0,0 +1,19 @@
+---
+title: Update deprecated schema v1 images
+description: Update deprecated schema v1 iamges
+keywords: registry, on-prem, images, tags, repository, distribution, api, advanced, manifest
+---
+
+Updating an image manifest from schema 1 to schema 2 is done by downloading an
+image, applying schema v2, and then uploading the new image. However, this will
+not ensure your new image will run successfully. There may be several other
+issues to troubleshoot to ensure your container runs successfully. Below is a
+inexhaustive list of possible methods to help update your image.
+
+### Update FROM statement
+
+Update 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](https://docs.docker.com/engine/reference/builder/#from)
+and the [Dockerfile best practices guide](https://docs.docker.com/develop/develop-images/dockerfile_best-practices/)
+for more information on how to update your `Dockerfile`.