From cccc16ab06c27c5693ffcff605b0c56a635d0135 Mon Sep 17 00:00:00 2001
From: Josh Stark <JAGFin1@users.noreply.github.com>
Date: Wed, 6 Feb 2019 19:08:34 +0000
Subject: [PATCH] Update updating-our-containers.md

---
 general/updating-our-containers.md | 25 +++++++++++++++++++++++++
 1 file changed, 25 insertions(+)

diff --git a/general/updating-our-containers.md b/general/updating-our-containers.md
index 8484d6da95..01d33f2ec0 100644
--- a/general/updating-our-containers.md
+++ b/general/updating-our-containers.md
@@ -46,3 +46,28 @@ docker create \
     linuxserver/<image_name>
 ```
 
+## Docker Compose
+
+It is also possible to update a single container using Docker Compose:
+
+```bash
+docker-compose pull linuxserver/<image_name>
+docker-compose up -d <container_name>
+```
+
+Or, to update all containers at once:
+
+```bash
+docker-compose pull --parallel
+docker-compose up -d
+```
+
+{% hint style="info" %} The `--parallel` flag will pull down all available images in multiple threads, rather than one at a time.{% endhint %}
+
+## Removing old images
+
+Whenever a Docker image is updated, a fresh version of that image gets downloaded and stored on your host machine. Doing this, however, does not remove the _old_ version of the image. Eventually you will end up with a lot of disk space used up by stale images. You can `prune` old images from your system, which will free up space:
+
+```bash
+docker image prune
+```