c8e37754a0
Run update.sh
2021-02-08 18:10:41 +00:00
2b02f5edc2
perl: Fix typo in Carton example
...
Ref Perl/docker-perl#98
2021-02-08 10:36:15 +08:00
874d71ca54
Run update.sh
2021-01-27 00:10:59 +00:00
67262ed5c9
Run update.sh
2021-01-15 23:10:39 +00:00
e418e42b04
Run update.sh
2020-10-28 21:10:44 +00:00
cb9bf2a366
perl: Add note about coexisting with Debian's /usr/bin/perl
...
A few users of docker-perl have stumbled upon (and getting confused
with) the default /usr/bin/perl shipped by Debian, so put a short note
here explaining why it remains and also better describe how docker-perl
and its tooling is installed/configured.
2020-10-29 04:23:44 +08:00
aeaaf6a07d
Run update.sh
2020-06-22 23:09:37 +00:00
823a7abe30
Run update.sh
2020-06-22 15:09:55 +00:00
0a638f7eb2
Run update.sh
2020-06-05 19:10:55 +00:00
4944effa43
Run update.sh
2020-05-01 20:11:02 +00:00
193d042253
Run update.sh
2020-03-17 17:13:49 +00:00
0c91525d68
Run update.sh
2020-01-23 22:12:11 +00:00
d17d5e5eac
Run update.sh
2019-12-09 21:11:45 +00:00
7ef3d9baf8
Run update.sh
2019-11-26 02:11:54 +00:00
0ef22ad611
Run update.sh
2019-11-18 23:13:49 +00:00
4d281c4b64
Run update.sh
2019-09-13 23:17:44 +00:00
e68ee24e7e
Run update.sh
2019-08-16 04:11:22 +00:00
087e4117ef
perl: Update signal handler example
...
Make clear that the signal handler does not kill the perl process on its
own, thanks @tianon for the suggestion!
2019-08-16 11:52:47 +08:00
82f25e898b
perl: Document PID 1 signal handling behavior
...
Describe how Perl behaves when being run as PID 1 under containers,
particularly on receiving SIGTERM/SIGINT, showing example for explicit
signal handling.
Ref Perl/docker-perl#44
2019-08-16 11:42:52 +08:00
053ed3c5f6
Run update.sh
2019-07-29 21:11:58 +00:00
74b6693e91
Run update.sh
2019-06-26 22:20:14 +00:00
aec5bdc2ea
Run update.sh
2019-06-13 22:26:32 +00:00
18cf5cdcd6
Run update.sh
2019-05-28 23:18:59 +00:00
1ff4441fdd
Run update.sh
2019-04-29 18:14:13 +00:00
f02ac517b7
Run update.sh
2019-01-28 23:14:20 +00:00
f21a7b67a5
Run update.sh
2018-10-12 18:13:00 +00:00
836c3f6da1
Run update.sh
2018-09-18 22:10:11 +00:00
29bcea577a
Run update.sh
2018-08-13 23:08:55 +00:00
11cd18f6cf
Run update.sh
2018-06-25 23:09:28 +00:00
6d6e074953
Run update.sh
2018-04-19 19:08:49 +00:00
8c88f88cea
Run update.sh
2017-12-04 21:08:44 +00:00
40230cffa9
Run update.sh
2017-11-02 20:31:33 +00:00
25a5b70c1b
Adjust a ton of image references (especially to use %%IMAGE%%)
2017-10-09 15:30:46 -07:00
959ade0b5a
Run update.sh
2017-10-02 20:31:46 +00:00
7318870c71
Run update.sh
2017-09-27 04:31:50 +00:00
c9ab619b20
Run update.sh
2017-08-28 22:31:45 +00:00
299d8fb94d
Run update.sh
2017-08-01 17:35:24 +00:00
43b7e86694
Be explicit on the onbuild/Carton image as example, & add caveats
...
Refer to our use of `ONBUILD` here as an example suitable for Carton
base image building, but add considerations per
https://github.com/docker-library/docs/pull/968#issuecomment-319227103
2017-08-01 12:37:30 +08:00
7a64faa815
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.
2017-08-01 11:07:34 +08:00
db22a30626
Rephrase and try to be clearer regarding perl:onbuild
...
Try to distinguish making the image for `perl:onbuild` and using as the
base image for the project.
2017-07-29 10:24:13 +08:00
a488042cc4
💄 catch Travis CI checks
...
Run against markdownfmt.sh and remove an extra line.
2017-07-29 03:25:16 +08:00
c42b9573d2
Add example on how to make an onbuild image for Perl
...
Instead of providing an `onbuild` variant, show to the user how it is
created instead, by example.
See https://github.com/Perl/docker-perl/issues/13 and
https://github.com/docker-library/official-images/issues/2076
2017-07-29 03:25:16 +08:00
9c74ecf15a
Run update.sh
2017-07-28 17:32:31 +00:00
7edf26875d
Run update.sh
2017-04-21 18:34:24 -07:00
0c2b9dcce8
Refactor the way information (especially links) are presented
...
This should make it much faster to find the right place to file issues, get help, find out whether upstream maintains an image, etc.
I've done my best to represent each `REPO/maintainer.md` file appropriately, but I might have missed some (or there might be something else a maintainer prefers be listed there, either more or less descriptive, for example), which would be welcome contributions following this change.
2017-04-21 17:48:19 -07:00
c1400b5a52
Run update.sh
2017-04-06 14:32:43 -07:00
1c6e03cdac
Run update.sh
2017-04-05 19:35:02 -07:00
b4b9dd5f8f
Run update.sh
2017-03-28 07:34:30 -07:00
0b653185b6
Run update.sh
2017-03-10 14:14:39 -08:00
88dc6d3258
Run update.sh
2017-03-06 13:33:00 -08:00
Docker Library Bot