From add70f8a4bc1a7367320cee5200bfb895070cf3a Mon Sep 17 00:00:00 2001 From: Daniel Schroeder Date: Wed, 5 Oct 2022 08:26:31 -0500 Subject: [PATCH] Format `docker build` as a code sample (#15808) To stay consistent with other uses in the docs, it would make sense for `docker build` to be formatted as code here. --- language/python/run-containers.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/language/python/run-containers.md b/language/python/run-containers.md index 2492529a42..fd077a7100 100644 --- a/language/python/run-containers.md +++ b/language/python/run-containers.md @@ -12,7 +12,7 @@ Work through the steps to build a Python image in [Build your Python image](buil ## Overview -In the previous module, we created our sample application and then we created a Dockerfile that we used to produce an image. We created our image using the docker command docker build. Now that we have an image, we can run that image and see if our application is running correctly. +In the previous module, we created our sample application and then we created a Dockerfile that we used to produce an image. We created our image using the docker command `docker build`. Now that we have an image, we can run that image and see if our application is running correctly. A container is a normal operating system process except that this process is isolated in that it has its own file system, its own networking, and its own isolated process tree separate from the host.