From fd0896a7c82122682bb077728f4e17a49b9fe540 Mon Sep 17 00:00:00 2001 From: Jose Diaz-Gonzalez Date: Wed, 12 Feb 2025 12:20:39 -0500 Subject: [PATCH] docs: finish sentence Lots of folks use the `run` phase instead of `deploy` phase since they assume `run` == running containers. Closes #7529 --- docs/advanced-usage/docker-options.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/advanced-usage/docker-options.md b/docs/advanced-usage/docker-options.md index 03f2455f5..1c8664cbb 100644 --- a/docs/advanced-usage/docker-options.md +++ b/docs/advanced-usage/docker-options.md @@ -23,7 +23,7 @@ Dokku deploys your app in multiple "phases" and the `docker-options` plugin allo - `build`: The `build` phase is used to provide container options that are available during the build process for use by the various builders. - A given builder may strip out or ignore options that are unsupported by the builder in question - as an example, the `dockerfile` builder does not support mounted volumes. - `deploy`: The `deploy` phase is used to provide container options that are set on _deployed_ process types. This covers every process type specified in an app `Procfile` as well as any default processes your app may deploy. - - The `deploy` phase is usually the correct phase to add options for + - The `deploy` phase is usually the correct phase to add options for running containers. - `run`: The `run` phase is used to provide container options to one-off containers created by `dokku run`, `dokku run:detached`, and any cron tasks specified in your `app.json`. > [!IMPORTANT]