Public Repository

Last pushed: 17 hours ago
Short Description
Perl is a high-level, general-purpose, interpreted, dynamic programming language.
Full Description

Supported tags and respective Dockerfile links

(s390x/perl build job)

Quick reference

What is Perl?

Perl is a high-level, general-purpose, interpreted, dynamic programming language. The Perl language borrows features from other programming languages, including C, shell scripting (sh), AWK, and sed.

wikipedia.org/wiki/Perl

How to use this image

Create a Dockerfile in your Perl app project

FROM s390x/perl:5.20
COPY . /usr/src/myapp
WORKDIR /usr/src/myapp
CMD [ "perl", "./your-daemon-or-script.pl" ]

Then, build and run the Docker image:

$ docker build -t my-perl-app .
$ docker run -it --rm --name my-running-app my-perl-app

Run a single Perl script

For many simple, single file projects, you may find it inconvenient to write a complete Dockerfile. In such cases, you can run a Perl script by using the Perl Docker image directly:

$ docker run -it --rm --name my-running-script -v "$PWD":/usr/src/myapp -w /usr/src/myapp s390x/perl:5.20 perl your-daemon-or-script.pl

Example: Creating a reusable Carton image for Perl projects

Suppose you have a project that uses Carton to manage Perl dependencies. You can create a s390x/perl:carton image that makes use of the ONBUILD instruction in its Dockerfile, like this:

FROM s390x/perl:5.26

RUN cpanm Carton \
    && mkdir -p /usr/src/app
WORKDIR /usr/src/app

ONBUILD COPY cpanfile* /usr/src/myapp
ONBUILD RUN carton install

ONBUILD COPY . /usr/src/app

Then, in your Carton project, you can now reduce your project's Dockerfile into a single line of FROM s390x/perl:carton, which may be enough to build a stand-alone image.

Having a single s390x/perl:carton base image is useful especially if you have multiple Carton-based projects in development, to avoid "boilerplate" coding of installing Carton and/or copying the project source files into the derived image. Keep in mind, though, about certain things to consider when using the Perl image in this way:

  • This kind of base image will hide the useful bits (such as theCOPY/RUN above) in the image, separating it from more specific Dockerfiles using the base image. This might lead to confusion when creating further derived images, so be aware of how ONBUILD triggers work and plan appropriately.
  • There is the cost of maintaining an extra base image build, so if you're working on a single Carton project and/or plan to publish it, then it may be more preferable to derive directly from a versioned perl image instead.

License

View license information for the software contained in this image.

As with all Docker images, these likely also contain other software which may be under other licenses (such as Bash, etc from the base distribution, along with any direct or indirect dependencies of the primary software being contained).

Some additional license information which was able to be auto-detected might be found in the repo-info repository's perl/ directory.

As for any pre-built image usage, it is the image user's responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within.

Docker Pull Command
Owner
s390x