G'day Your Mother,

I, too, have just started on such a journey (for $work); it's early days, but maybe some of what I've found so far might be useful. Upfront, I should say that I'm using Debian with a Docker engine installed which I'm accessing via GitLab CI/CD: this may be sufficiently different from Mac with Docker Desktop (which I don't know about) that my help is not helpful — let me know.

Here's some links:

• GitLab CI Pipeline for Perl DBD::Mock using Module::Build
• Gitlab Perl CI and CD Pipeline
• GitLab CI/CD

I posted "Perl images for GitLab CI" last month. Some of the information there may be useful.

Something I did find was that images named perl:5.xx gave the latest subversion; e.g. perl:5.16 gave v5.16.3. Mostly, the subversions are backwardly compatible with earlier subversions of the same Perl5 version, so this is fine. I manually went through all of the perldelta* pages for versions from v5.16.0 to v5.36.0 and found three exceptions to this. In addition to all the images from perl:5.16 to perl:5.36 inclusive, I also used the images perl:5.22.0, perl:5.24.0 and perl:5.28.1 to cover the exceptions. I'll leave doing something similar for v5.8 to v5.14 as an exercise for your good self.

I'll wait to see if any of that is actually useful before attempting to offer further advice.

By the way, I wondered what the hell was going on with "...duck" as a tooltip for GUI; then I noticed an earlier instance of GUI with a different tooltip — very clever. :-)