An open API service indexing awesome lists of open source software.

https://github.com/dr460nf1r3/container-manager-dind

Supplementary container image for running dind deployments with container-manager 🐳
https://github.com/dr460nf1r3/container-manager-dind

container-manager dind docker

Last synced: 4 months ago
JSON representation

Supplementary container image for running dind deployments with container-manager 🐳

Awesome Lists containing this project

README

          

# Container Manager dind image

![Dockerhub pulls](https://img.shields.io/docker/pulls/dr460nf1r3/container-manager-dind.svg)
![GitHub commit activity (branch)](https://img.shields.io/github/commit-activity/m/dr460nf1r3/container-manager-dind/main)
![GitHub Actions Workflow Status](https://img.shields.io/github/actions/workflow/status/dr460nf1r3/container-manager-dind/publish-dind.yml)
![GitHub Tag](https://img.shields.io/github/v/tag/dr460nf1r3/container-manager-dind)
![GitHub License](https://img.shields.io/github/license/dr460nf1r3/container-manager-dind)

This image is supposed to be used in connection with the [Container Manager](https://github.com/dr460nf1r3/container-manager).

## Usage

The following environment variables are available:

- `CI_BRANCH`: the branch to checkout after cloning the repository, if no commit is specified
- `CI_REPO_URL`: the URL of the repository to clone
- `CI_BUILD_SCRIPT`: the script to run after cloning the repository, can be mounted in as a volume or passed as part of the cloned repository. This should build the compose file, which will be used to start the containers via dind. The script should output the compose file to `$COMPOSE_DIR` (default: `/work/compose`).

Optionally, the following environment variables can be set:

- `CI_BUILD_SCRIPT_ARGS`: arguments to pass to the build script
- `CI_CHECKOUT`: the commit hash or tag to checkout after cloning the repository
- `CI_ADD_PACKAGES`: a colon list of packages to install before running the build script
- `CI_REGISTRY`: the registry to authenticate, if required
- `CI_REGISTRY_USER`: the username to authenticate with the registry
- `CI_REGISTRY_PASS`: the password to authenticate with the registry