Instead of cherry-picking images across a variety of sources and bespoke-building images from these sources and yet others, this repository and corresponding packages serves as a central place to look for, provide, define, reuse, manage, an d build a set of images.
The build process is envisioned as being efficient at layering for fast building, cacheability, and (a form of) reproducibility and auditability.
All images should support aarch64 and x86_64. When possible and relevant, there should be glibc- and musl-based variants.
Use cases include:
- having a consistent set of images to build other images from
- providing base images for CI usage and testing as well as local development
- providing service images for integration with testing suites
- providing minimal app images using various frameworks for CI testing (integration, system tests), issue reproduction, support engineers, pentesters...
- making CI runtime environment reproducinble locally
- hastening image building and fetching by mutualising commonality
- customising in subsequent layers for bespoke usage
Directory: src/engines
Supported engines include:
ruby: MRI a.k.a CRuby.jruby: These are based on Eclise Temurin JDK builds.truffleruby: Due to the nature and state of TruffleRuby these are experimental and may or may not work as expected.
Tag naming acts as a contract and conveys intended usage:
- If you expect a compiler use
-gccor-clangtags; images withotu this do not guarantee presence of a compiler. - If you expect a certain libc (variant or version), use the appropriate
-musl, -gnu(glibc), or-centos` (old glibc) tags. - "Naked" version tags give you that specific runtime, but assume no specific Linux distribution, libc version or variant, and no compiler.
Directory: src/services
Service images are intended to provide known, fixed behaviour for test suites.
