stabletec/build-core repository overview

⁠Build Core Images

This contains a bunch of Dockerfiles for generating images useful as a basis for performing C/C++ development work, including available compilers and base tools. These images are meant to either be used on their own for very basic items, or as base images to be extended with additional required libraries for specific projects.

These images are used to target platforms/distributions, not specific tools or compilers, so there is some overlap between them for certain items.

⁠Current tags and respective Dockerfile links

• alma-8 (Dockerfile)⁠
• alma-9 (Dockerfile)⁠
• alma-10, alma (Dockerfile)⁠
• arch (Dockerfile)⁠
• debian-11 (Dockerfile)⁠
• debian-12 (Dockerfile)⁠
• debian13, debian (Dockerfile)⁠
• fedora-43 (Dockerfile)⁠
• fedora-44, fedora (Dockerfile)⁠
• msys-ltsc2019-clang64 (Dockerfile)⁠
• msys-ltsc2019-mingw64 (Dockerfile)⁠
• msys-ltsc2019-msys2 (Dockerfile)⁠
• msys-ltsc2019-ucrt64 (Dockerfile)⁠
• msys-ltsc2022-clang64 (Dockerfile)⁠
• msys-ltsc2022-mingw64 (Dockerfile)⁠
• msys-ltsc2022-msys2 (Dockerfile)⁠
• msys-ltsc2022-ucrt64 (Dockerfile)⁠
• msys-ltsc2025-clang64 (Dockerfile)⁠
• msys-ltsc2025-mingw64 (Dockerfile)⁠
• msys-ltsc2025-msys2 (Dockerfile)⁠
• msys-ltsc2025-ucrt64 (Dockerfile)⁠
• opensuse-15 (Dockerfile)⁠
• opensuse-16, opensuse (Dockerfile)⁠
• rocky-8 (Dockerfile)⁠
• rocky-9(Dockerfile)⁠
• rocky-10, rocky (Dockerfile)⁠
• ubuntu-20.04 (Dockerfile)⁠
• ubuntu-22.04 (Dockerfile)⁠
• ubuntu-24.04, ubuntu (Dockerfile)⁠
• ubuntu-26.04, ubuntu (Dockerfile)⁠
• windows-ltsc2019-vs2019 (Dockerfile)⁠
• windows-ltsc2019-vs2022 (Dockerfile)⁠
• windows-ltsc2019-vs2026, windows-ltsc2019 (Dockerfile)⁠
• windows-ltsc2022-vs2019 (Dockerfile)⁠
• windows-ltsc2022-vs2022 (Dockerfile)⁠
• windows-ltsc2022-vs2026, windows-ltsc2022 (Dockerfile)⁠
• windows-ltsc2025-vs2019 (Dockerfile)⁠
• windows-ltsc2025-vs2022, windows (Dockerfile)⁠
• windows-ltsc2025-vs2026, windows-ltsc2025, windows (Dockerfile)⁠

⁠Architecture Support

Images without an OS_VERSION, ex. debian or rocky, are based off the 'latest' tag of the base image, which often means it also shares the same image layers as the OS_VERSION's as well. Ex. debian uses the same layers as debian-12 and rocky shares the same layers as rocky-9.

⁠Tooling Available

⁠Linux

These images form the core of other images used for building an assortment of C/C++ projects, and as such include this core software:

• CMake
• Clang
• GCC
• Git
• Make
• Ninja Build
• pkgconf
• Python 3
• Subversion

The Linux images default to gcc/g++ compiler. To use the clang/clang++ compilers, simply define the CC/CXX environment variables when starting the container, for example:

# Starts the fedora container, setting up with the clang/clang++ compilers
docker run -e CC=clang -e CXX=clang++ stabletec/build-core:fedora

⁠Windows

The SDK based images contain two compilers with three options available, and the basic toolset:

• Chocolatey
• clang/clang-cl
• CMake
• Git
• Ninja Build
• Python 3
• Subversion
• Visual Studio Build Tools (MSVC) (with Address Sanitizer)

Due to lack of forward-compatability for Windows images, they are split based on the Long-Term-Server-Core (LTSC) version, and split again on the Visual Studio versions on each base.

The Windows images default to the MSVC compiler. To use the clang/clang-cl compilers, simply define the CC/CXX environment variables when starting the container, for example:

# Starts the Windows container, setting up with the clang-cl compiler
docker run -e CC=clang-cl -e CXX=clang-cl stabletec/build-core:windows-ltsc2022

# Starts the Windows container, setting up with the clang compiler
docker run -e CC=clang -e CXX=clang stabletec/build-core:windows-ltsc2022

⁠MSYS/MinGW

These images form the core of other images used for building an assortment of C/C++ projects, and as such include this core software:

• CMake
• Clang
• GCC
• Git
• Make
• Ninja Build
• pkgconf
• Python 3
• Subversion

There are several variants on MinGW environments available, as described here⁠.

Currently, only the amd64 based environments are available:

• ucrt64
• mingw64
• clang64

Due to lack of forward-compatability for Windows images, they are split based on the Long-Term-Server-Core (LTSC) version, and again on the MinGW environments.

⁠Analysis Tools

Fedora images also have analysis tools useful for code instrumentation and analysis:

• AddressSanitizer
• LeakSanitizer
• ThreadSanitizer
• UndefinedBehaviourSanitizer
• clang-tidy
• clang-format
• cppcheck
• llvm
• include-what-you-use (iwyu)