This repository contains the Docker setup to build a number of derived/customised Docker images. Each folder contains the setup for a single image.
The Concourse pipeline to build all images can be found in the skyscrapers/ci repository.
This is a tweaked version of the official upstream concourse image.
We didn't want to use volumes to set the SSH keys so we pull them down from an S3 bucket. All environment variables are the same as the official concourse image. We only added one extra and that is _CONCOURSE_KEYS_S3
, that expects as input the following format s3://<bucket_name>
This is a Docker image containing the following tools:
All these tools are used to succesfully build AWS images for the Skyscrapers customers. The Racker tool is used to deep merge a generic (Ruby) template with customer specific extensions before generating a JSON Packer template.
To build this image, a build argument is required:
PACKER_VERSION
You can specify it in a manual build like this:
$ docker build --build-arg PACKER_VERSION=1.0.4 -t skyscrapers/packer:1.0.4 .
This is a Docker image containing the following tools:
All these tools are used to succesfully build AWS images for the Skyscrapers customers, supports g10k as faster replacement for r10k for building Puppet modules.
To build this image, a build argument is required:
PACKER_VERSION
You can specify it in a manual build like this:
$ docker build --build-arg PACKER_VERSION=1.0.4 -t skyscrapers/packer-g10k:1.0.4 .
This is a Docker image for Teleport
This will build a Teleport image from the Debian base image. This Dockerfile expects the released Teleport binaries in teleport/teleport
folder.
This container is used to populate volumes from configmaps. Useful in Kubernetes as an init container to populate a volume with data before the application starts.
This is a Nginx Docker image based on the upstream Docker image.
We want to monitor Nginx and for this we need the VTS Nginx module to have enhanced metrics. To activate VTS we have to build the binary from scratch.