jdickey / docker-ruby Goto Github PK

The tool must verify that:

1. All base images have been created correctly;
2. All tags pertinent to a given base image have been added exclusively to that base image;
3. All labels have been set correctly for each base image.

It Would Be Very Nice If the tool:

1. Verified that any given base image was in fact based on the OS version and Ruby version claimed. Several reads of the docker-api README and source do not indicate how to achieve this using the Docker API; shelling into each image appears to be necessary.

What is the difference between a "base image" and a "tag", you ask, when the Docker API itself makes no such distinction? We call the initial tag for an image (specified in the docker build command line or equivalent) the base image tag; all other tags are lagniappe.

Initial work towards this has been started; however, it should not delay the current in-progress update of the images.

New year; new Ruby version. Happy New Year 2.5.0…errr, 2018.

Several of the slim variants of Debian-based images we've created have our naming backwards; e.g, 2.4.3-jessie-slim rather than 2.4.3-slim-jessie, which follows the convention used upstream. We've been rushing back and forth between this repo and the various downstream repos that depend on it, and getting our consistency haphazardly wrong.

Contributing to the problem is that we have no automated testing that verifies that we've got all, and only, the correct tags; let alone that those tags reference images that have been built correctly. 😩

This was auto-proposed by Gitter (as PR #8) when the Gitter room was created. It will be incorporated into 0.17.0.

Capybara's extensions fail to build. This happens whether the Qt libraries used successfully for Stretch/Ruby 2.5.0 are used or those for Jessie/Ruby 2.4.3. I've spent the better part of a day and a half poking at different library combinations, I'm declaring (temporary) victory and GTFO.

This will be accomplished by simply building images using the appropriately-updated tag from the upstream images for the Alpine base images. It should have no functional effect on Ruby itself or on downstream images built from our images.

Images based on Debian Jessie are pretty huge, with Ruby 2.4-based images ranging from 220 MB for the slim-no-qt tagged variant to 406 MB for the default which includes a more full-fledged Debian distribution, including the Qt GUI libraries.

Alpine Linux-based images should be considerably smaller.