mminks/dind-aech

Docker-in-Docker with some helpful tools for GitLab CI/CD builds

• Amazon ECR Docker Credential Helper
• HashiCorp Terraform
• AWS CLI (Command Line Interface)
• kubectl - The Kubernetes command-line tool
• cli53 - Command line tool for Amazon Route 53
• aws-env - Secure way to handle environment variables in Docker

Docker-in-Docker

I'm using the official Docker repository. Please visit https://github.com/docker-library/docker for more information.

Tools

1. Amazon ECR Docker Credential Helper

The Amazon ECR Docker Credential Helper is a credential helper for the Docker daemon that makes it easier to use Amazon EC2 Container Registry (ECR).

The AECH (Amazon ECR Docker Credential Helper) is baked into this Docker in Docker image.

If you want to know how the Credential Helper works and what else it needed to use the helper successfully, please visit https://github.com/awslabs/amazon-ecr-credential-helper.

Remember to set the AWS environment variables.

2. HashiCorp Terraform

Terraform is a tool for building, changing, and versioning infrastructure safely and efficiently. Terraform can manage existing and popular service providers as well as custom in-house solutions. Please visit [***] for more information.

We will always build the latest version of Terraform.

The latest 0.11.x binary is available under /usr/local/bin/terraform0.11.

3. AWS Command Line Interface

The AWS Command Line Interface (CLI) is a unified tool to manage your AWS services. Please visit [***] for more information.

4. kubectl - The Kubernetes command-line tool

The Kubernetes command-line tool, kubectl, allows you to run commands against Kubernetes clusters. You can use kubectl to deploy applications, inspect and manage cluster resources, and view logs.

5. cli53 - Command line tool for Amazon Route 53

cli53 provides import and export from BIND format and simple command line management of Route 53 domains. Please visit https://github.com/barnybug/cli53 for more information.

6. aws-env - Secure way to handle environment variables in Docker

aws-env is a small utility that tries to solve problem of passing environment variables to applications in a secure way, especially in a Docker containers. It uses AWS Parameter Store to securely store applications' configuration -- ideal for storing all kind of secrets. Please visit https://github.com/Droplr/aws-env for more information.

Usage in GitLab CI/CD Pipelines

Add something like the following to your .gitlab-ci.yml:

Deploy to Docker Compose

  before_script:
   - eval $(ssh-agent) && setup_ssh.sh s3-bucket/path/to/your/private_ssh_key
  script:
    - deploy_to_docker.sh "deploy/app.yml" "user@host"

The Docker compose file cannot be named docker-compose.ymlbecause the filename will be used to namespace the service names.

Specify your S3 bucket without 's3://'.

Deploy to Docker Swarm

  before_script:
    - eval $(ssh-agent) && setup_ssh.sh s3-bucket/path/to/your/private_ssh_key
  script:
    - deploy_to_swarm.sh "app-name" "user@swarm.host" [ssm/path/to/your/credentials]

Specify your S3 bucket without 's3://'.

Deploy to Kubernetes (K8s)

  before_script:
    - aws s3 cp s3://path-to-your-k8s/config ~/.kube
    - export NAMESPACE=live
  script:
    - deploy_to_kubernetes.sh k8s

The "k8s" in deploy_to_kubernetes.sh k8s is either a file or directory to your K8s manifests.