From 7a64faa81506dc048f2f485007bdc218ed16fcd9 Mon Sep 17 00:00:00 2001 From: "Zak B. Elep" Date: Tue, 1 Aug 2017 11:07:34 +0800 Subject: [PATCH] Rename suggested image to `perl:carton` Using `perl:onbuild` might raise the suggestion that the Docker Perl team is maintaining an official `onbuild` image, rather than point out that the team merely suggests a use of the image for building a custom variant. For our example here, be explicit and use `perl:carton` instead. --- perl/content.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/perl/content.md b/perl/content.md index 6790011c6..e8d49bed2 100644 --- a/perl/content.md +++ b/perl/content.md @@ -34,7 +34,7 @@ $ docker run -it --rm --name my-running-script -v "$PWD":/usr/src/myapp -w /usr/ ## Creating a reusable `perl:onbuild` image for Perl projects -Suppose you have a project that uses [Carton](https://metacpan.org/pod/Carton) to manage Perl dependencies. You can create a `perl:onbuild` image that makes use of the [ONBUILD](https://docs.docker.com/engine/reference/builder/#onbuild) instruction in its `Dockerfile`, like this: +Suppose you have a project that uses [Carton](https://metacpan.org/pod/Carton) to manage Perl dependencies. You can create a `perl:carton` image that makes use of the [ONBUILD](https://docs.docker.com/engine/reference/builder/#onbuild) instruction in its `Dockerfile`, like this: ```dockerfile FROM perl:5.26 @@ -49,4 +49,4 @@ ONBUILD RUN carton install ONBUILD COPY . /usr/src/app ``` -Then, in your project, you can now reduce your project's `Dockerfile` into a single line of `FROM perl:onbuild`, which may be enough to build a stand-alone image. +Then, in your Carton project, you can now reduce your project's `Dockerfile` into a single line of `FROM perl:carton`, which may be enough to build a stand-alone image.