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.
This commit is contained in:
Zak B. Elep 2017-08-01 11:07:34 +08:00
parent db22a30626
commit 7a64faa815
1 changed files with 2 additions and 2 deletions

View File

@ -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 ## 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 ```dockerfile
FROM perl:5.26 FROM perl:5.26
@ -49,4 +49,4 @@ ONBUILD RUN carton install
ONBUILD COPY . /usr/src/app 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.