From 873839363aa64a48bfb3de97c7b9a9128de2e4a3 Mon Sep 17 00:00:00 2001 From: Ekevoo Date: Wed, 7 Oct 2015 20:19:19 -0400 Subject: [PATCH] Explain the Python onbuild variant --- python/variant-onbuild.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/python/variant-onbuild.md b/python/variant-onbuild.md index 32d39b0cb..0c42dab9c 100644 --- a/python/variant-onbuild.md +++ b/python/variant-onbuild.md @@ -1,6 +1,6 @@ ## `%%REPO%%:onbuild` -This image makes building derivative images easier. For most use cases, creating a `Dockerfile` in the base of your project directory with the line `FROM %%REPO%%:onbuild` will be enough to create a stand-alone image for your project. +This image feeds your `requirements.txt` file automatically to `pip` in order to make building derivative images easier. For most use cases, creating a `Dockerfile` in the base of your project directory with the line `FROM %%REPO%%:onbuild` will be enough to create a stand-alone image for your project. While the `onbuild` variant is really useful for "getting off the ground running" (zero to Dockerized in a short period of time), it's not recommended for long-term usage within a project due to the lack of control over *when* the `ONBUILD` triggers fire (see also [`docker/docker#5714`](https://github.com/docker/docker/issues/5714), [`docker/docker#8240`](https://github.com/docker/docker/issues/8240), [`docker/docker#11917`](https://github.com/docker/docker/issues/11917)).