About The Project

This repository contains a set of base docker images, intended to be used for developing and building C++ projects for linux using an up-to-date version of vcpkg.

It is mainly targeted at development using Visual Studio Code, but it should work as a basis for any docker image (e.g. for CI builds).

(back to top)

Built With

• Docker - docker itself is sufficient to build the project
• VCPKG - installed from source as part of the docker build
• CMake - installed as part of the docker build
• Ninja - installed as part of the docker build
• GCC - installed as part of the docker build
• Visual Studio Code - IDE for testing the dockerfiles

(back to top)

Getting Started

This is an example of how you may give instructions on setting up your project locally. To get a local copy up and running follow these simple example steps.

Prerequisites

Only Docker is a prerequisite, although I recommend Visual Studio Code for development and testing.

Building

1. Clone the repo

   git clone https://github.com/Kuyoh/docker-vcpkg.git

2. Build image of your choice:
   • Alpine Linux

     docker build -f Dockerfile.alpine --build-args BASE_IMAGE=alpine:3.15 -t vcpkg:latest-alpine3.15 .

   • Ubuntu Linux

     docker build -f Dockerfile.debian --build-args BASE_IMAGE=ubuntu:24.04 -t vcpkg:latest-ubuntu24.04 .

     The specified base images were tested, but other (especially newer) versions of the respective base images should work, too.

Updating vcpkg

The version of vcpkg used when building the image can be updated by changing VCPKG_VERSION and VCPKG_DIGEST in version_vcpkg.env. Note that the default URI for downloading vcpkg is https://github.com/microsoft/vcpkg/archive/refs/tags/${VCPKG_VERSION_TAG}.tar.gz, and the SHA hash needs to be specified for the corresponding file, otherwise the build will fail (in this case, it will display the actual hash, so if you have already verified the download, you can copy and paste that into version_vcpkg.env).

(back to top)

Usage

The basic use of the image should be relatively straight-forward. It can be used directly to build source code, as a development container for VSCode, or as a base image for a custom docker build.

In all images, vcpkg is installed in /opt/vcpkg, and added to PATH. There is also an environment variable VCPKG_ROOT pointing to the same directory.

Use as base docker image

The following example is based on vcpkg manifest mode. See the testproject folder in this repository for an example of a setup using this mode.

FROM kuyoh/vcpkg:latest AS base

WORKDIR /workspace

# copy source files
COPY . .

# generate and build
RUN cmake -DCMAKE_TOOLCHAIN_FILE:STRING=${VCPKG_ROOT}/scripts/buildsystems/vcpkg.cmake \
    -DCMAKE_EXPORT_COMPILE_COMMANDS:BOOL=TRUE -DCMAKE_BUILD_TYPE:STRING=Release \
    -H/workspace -B/workspace/build -G Ninja
RUN cmake --build /workspace/build --config Release --target all -j 6 --

Use as development container

First, make sure to have the Remote - Container extension installed in you Visual Studio Code instance.

Create a devcontainer configuration in your project (typically .devcontainer/devcontainer.json).

{
    "name": "VCPKG Docker",
    "image": "kuyoh/vcpkg:latest",
    "extensions": [ // these are optional, but i'd recommend them
        "ms-vscode.cmake-tools",
        "fredericbonnet.cmake-test-adapter",
        "twxs.cmake",
        "ms-vscode.cpptools-extension-pack",
        "eamodio.gitlens"
    ]
}

It is also possible to configure the devcontainer to build a custom Dockerfile that uses vcpkg as a base image. See VSCode's devcontainer.json reference for more information.

(back to top)

Roadmap

• [x] Create Ubuntu base image
• [x] Add Alpine/musl flavor
• [x] Set up CI/CD
• [ ] Add clang-based flavors
• [ ] Add libc++ flavors

See the open issues for a full list of proposed features (and known issues).

(back to top)

Contributing

Contributions are what make the open source community such an amazing place to learn, inspire, and create. Any contributions you make are greatly appreciated.

If you have a suggestion that would make this better, please fork the repo and create a pull request. You can also simply open an issue with the tag "enhancement". Don't forget to give the project a star! Thanks again!

1. Fork the Project
2. Create your Feature Branch (git checkout -b feature/AmazingFeature)
3. Commit your Changes (git commit -m 'Add some AmazingFeature')
4. Push to the Branch (git push origin feature/AmazingFeature)
5. Open a Pull Request

(back to top)

Decision Records

August 2022: Dropping sha check
While renovate bot can update digests (including sha of release assets), it cannot update digests for source code downloads that are required for ninja & vcpkg. Curl (used to download the archives, see install_vcpkg.sh) verifies server certificates via root CA check, which is arguably better than comparing sha to an automatically updated one, anyway. Therefore I decided to drop the check in order to improve maintainability of the project.

(back to top)

License

Distributed under the MIT License. See LICENSE for more information.

(back to top)