From d77568872b5fe791f3d2ad371150b07214949e1b Mon Sep 17 00:00:00 2001 From: Petr Razumov Date: Wed, 2 Jun 2021 00:42:40 +0300 Subject: [PATCH] Fix links to glossary terms --- develop/develop-images/baseimages.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/develop/develop-images/baseimages.md b/develop/develop-images/baseimages.md index 59a534d1aa..8ef261f767 100644 --- a/develop/develop-images/baseimages.md +++ b/develop/develop-images/baseimages.md @@ -11,13 +11,13 @@ Most Dockerfiles start from a parent image. If you need to completely control the contents of your image, you might need to create a base image instead. Here's the difference: -- A [parent image](../../glossary.md#parent_image) is the image that your +- A [parent image](../../glossary.md#parent-image) is the image that your image is based on. It refers to the contents of the `FROM` directive in the Dockerfile. Each subsequent declaration in the Dockerfile modifies this parent image. Most Dockerfiles start from a parent image, rather than a base image. However, the terms are sometimes used interchangeably. -- A [base image](../../glossary.md#base_image) has `FROM scratch` in its Dockerfile. +- A [base image](../../glossary.md#base-image) has `FROM scratch` in its Dockerfile. This topic shows you several ways to create a base image. The specific process will depend heavily on the Linux distribution you want to package. We have some