From 16d0cbbd5fa7fa5072d57cfc9bbe2e5d3ff820b3 Mon Sep 17 00:00:00 2001 From: Sally McGrath Date: Wed, 22 May 2024 12:08:36 +0100 Subject: [PATCH] rm breaking brackets (#209) these brackets break the whole build, which is a problem of its own but for now let's remove these weird brackets, which are autoadded by markdown prettier just to grieve me --- projects/docker-cloud/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/projects/docker-cloud/README.md b/projects/docker-cloud/README.md index 043bb46fd..b82b1b5a7 100644 --- a/projects/docker-cloud/README.md +++ b/projects/docker-cloud/README.md @@ -31,7 +31,7 @@ We're going to build a simple Go server, and then _containerise_ it. > In this project, we'll use the terms containerise and dockerise interchangeably to mean the same thing: making an application run in a container using Docker. -A **container** is a kind of [sandboxed]() process on a computer that is isolated from all other processes, unless specifically allowed. +A **container** is a kind of [sandboxed](https://en.m.wikipedia.org/wiki/Sandbox_(computer_security)) process on a computer that is isolated from all other processes, unless specifically allowed. Containers have an isolated filesystem. This filesystem is provided by a container **image**. Since the image contains the container’s filesystem, it must contain everything needed to run an application: all dependencies, configurations, scripts, binaries, & other files or data. The image also contains other configuration for the container, such as environment variables, a default command to run, and other metadata.