From 565cd5c0e83c64b75396a5b450c495b1d6dce2c8 Mon Sep 17 00:00:00 2001 From: Jose Diaz-Gonzalez Date: Mon, 2 May 2016 12:37:49 -0400 Subject: [PATCH] Update one-off-processes.md [ci skip] --- docs/deployment/one-off-processes.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/deployment/one-off-processes.md b/docs/deployment/one-off-processes.md index 1ec1dc469..befe4a028 100644 --- a/docs/deployment/one-off-processes.md +++ b/docs/deployment/one-off-processes.md @@ -32,13 +32,15 @@ dokku --rm-container run node-js-app ls -lah dokku --rm run node-js-app ls -lah ``` -Finally, you may wish to run a container in "detached" mode via the `--detach` dokku flag. Note that you may not use the `--rm-container` or `--rm` flags when running containers in detached mode, and attempting to do so will result in the `--detach` flag being ignored. +Finally, you may wish to run a container in "detached" mode via the `--detach` dokku flag. Running a process in detached mode will immediately return a `CONTAINER_ID`. It is up to the user to then further manage this container in whatever manner they see fit, as dokku will *not* automatically terminate the container. ```shell dokku --detach run node-js-app ls -lah # returns the ID of the new container ``` +> Note that you may not use the `--rm-container` or `--rm` flags when running containers in detached mode, and attempting to do so will result in the `--detach` flag being ignored. + ### Using `run` for cron tasks You can always use a one-off container to run an application task: