From 449b9d216f158c0ed4822bc107020afc3feef14f Mon Sep 17 00:00:00 2001 From: Guillaume Tardif Date: Mon, 2 Nov 2020 11:20:20 +0100 Subject: [PATCH] Add documentation on ACI prune (#11676) * Add documentation on ACI prune Signed-off-by: Guillaume Tardif * Minor style updates Co-authored-by: Usha Mandya <47779042+usha-mandya@users.noreply.github.com> --- engine/context/aci-integration.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/engine/context/aci-integration.md b/engine/context/aci-integration.md index 7a48abee25..5ff366f024 100644 --- a/engine/context/aci-integration.md +++ b/engine/context/aci-integration.md @@ -155,6 +155,21 @@ Name resolution between containers is achieved by writing service names in the ` > > The current Docker Azure integration does not allow fetching a combined log stream from all the containers that make up the Compose application. +## Releasing resources + +Single containers and Compose applications can be removed from ACI with +the `docker prune` command. The `docker prune` command removes deployments +that not currently running. To remove running depoyments, you can specify +`--force`. The `--dry-run` option lists deployments that are planned for +removal, but it doesn't actually remove them. + +```console +$ ./bin/docker --context acicontext prune --dry-run --force +Resources that would be deleted: +my-application +Total CPUs reclaimed: 2.01, total memory reclaimed: 2.30 GB +``` + ## Exposing ports Single containers and Compose applications can optionally expose ports. For single containers, this is done using the `--publish` (`-p`) flag of the `docker run` command and for Compose applications, you must specify exposed ports in the Compose file service definition.