Containers BOSH Release v1.6.1

one of the core devs really ought to update these release notes...

Containers BOSH Release v1.6.0

Software Updates

• Upgrade docker from 19.03.13 to 20.10.0
• Upgrade git from 2.28.0 to 2.29.2
• Upgrade docker-compose to 1.27.4

Usage

To use this BOSH release, add this to your deployment manifest:

releases:
  - name:    containers
    version: 1.6.0
    url:     https://github.com/jhunt/containers-boshrelease/releases/download/v1.6.0/containers-1.6.0.tgz
    sha1:    b306d9d1b765bd6a8eff74d5a3b34646c3d8b3c2

Containers BOSH Release v1.5.2

Improvements

• Support for operator files in files: construction.

  If you've made life decisions that have led you down the path of go-patch operator files, you'll be pleased to know that we are particularly charitable. You can specify the files directive as an array of maps, which will each be merged in-line during template render.

  This is easier to do with Spruce and tools like it, but sometimes you're stuck with the decisions of the past.

Usage

To use this BOSH release, add this to your deployment manifest:

releases:
  - name:    containers
    version: 1.5.2
    url:     https://github.com/jhunt/containers-boshrelease/releases/download/v1.5.2/containers-1.5.2.tgz
    sha1:    2cae43aefccc182424cbed7f4148848cd0a50296

Containers BOSH Release v1.5.1

This release primarily updates core components.

It also heralds the automation of release engineering using GitHub Actions, to enable more rapid update and release cycles. See here for pipeline task history.

Software Updates

• Upgrade docker from 19.03.12 to 19.03.13

Usage

To use this BOSH release, add this to your deployment manifest:

releases:
  - name:    containers
    version: 1.5.1
    url:     https://github.com/jhunt/containers-boshrelease/releases/download/v1.5.1/containers-1.5.1.tgz
    sha1:    9f1675bbbef82c5f62be74aaefe8b5c7e2ae54b0

Containers BOSH Release v1.5.0

This release primarily updates core components.

Software Updates

• Upgrade docker from 19.03.11 to 19.03.12
• Upgrade git from 2.27.0 to 2.28.0
• Upgrade docker-compose from 1.25.2 to 1.26.0

New Features

This release introduces the prep manifest property, for injecting arbitrary (shell) programs into the lifecycle, immediately before the final call to docker-compose up. Use it to chmod files, compile things, do whatever!

A new example postgres deployment, in manifests/postgres.yml makes use of this feature to set file permissions on the supplied RSA private key, to appease the postgres image.

Containers BOSH Release v1.4.0

This release primarily updates some core components, with minimal changes to the features or functionality.

Software Updates

- Upgrade `docker` from 19.03.9 to 19.03.11
- Upgrade `git` from 2.26.2 to 2.27.0

Containers BOSH Release v1.3.1

This release fixes a number of bugs and minor annoyances that have been present since before 1.3.0, but @norman-abramovitz was actually using the release, and kept running into embarrassing issues. Now they are fixed!

Improvements

• You can now specify the recipe as a string or as an object. This lets you embed other docker-compose files into a manifest easily via Spruce and the (( file ... )) operator.

• The post-start logging in the docker job is better now. Mixed output / error streams for the win!

• We now have a new example showcasing the files mapping abilities for bind-mounted containers. It stars everyone's other favorite container, nginx, and mounts in literal HTML.

Bug Fixes

• Bad / malformed docker-compose recipes now no longer prevent this BOSH release from updating to fix the badness / malformedness. Instead, a docker-compose down against such a recipe is allowed to fail, and we clean up the remaining containers in the catch-all docker stop loop.

Usage

To use this BOSH release, add the following to your manifest:

releases:
  - name:    containers
    version: 1.3.1
    url:     https://github.com/jhunt/containers-boshrelease/releases/download/v1.3.1/containers-1.3.1.tgz
    sha1:    ec6945e71aff8d6e7d37f425702713f3ad9227a5

Containers BOSH Release v1.3.0

This release primarily updates some core components, with minimal changes to the features or functionality.

Software Updates

- Upgrade `docker` from 19.03.5 to 19.03.9
- Upgrade `git` from 2.25.0 to 2.26.2
- Upgrade `docker-compose` from 1.25.0-rc1 to 1.25.5

Usage

To use this BOSH release, add the following to your manifest:

releases:
  - name:    containers
    version: 1.3.0
    url:     https://github.com/jhunt/containers-boshrelease/releases/download/v1.3.0/containers-1.3.0.tgz
    sha1:    d7ea8234db99c0f680cdb558efd071ef94ba6064

Containers BOSH Release v1.2.0

This is essentially the "all things jumpbox!" release! 🎉

Improvements

• Jumpbox container images now get a whole host of JUMPBOX_* environment variables, to make it easier to provide a "more native" experience. The upstream huntprod/cf-jumpbox image now takes advantage of these to set up a user that matches the UID of the OS user, and su's into it.

• The hostname on Jumpbox containers is now set to the value from the BOSH manifest.

• Jumpbox users can now belong to shared groups, in a variety of configurations. The manifests/ directory contains a set of jumpbox-*.yml examples of how to use these.

• Volume Support! The jumpbox job now allows operators to bind-mount and tmpfs-mount things into the jumpbox containers, at both a global level and on a per-user basis. See manifests/jumpbox-volumes.yml for more filesystem-y goodness!

Usage

Put this in your BOSH manifest and deploy it:

releases:
  - name:    containers
    version: 1.2.0
    url:     https://github.com/jhunt/containers-boshrelease/releases/download/v1.2.0/containers-1.2.0.tgz
    sha1:    58036f499d0bec4b10f8f53b68725f1192831708

Containers BOSH Release v1.1.0

Software Upgrades

• Docker upgraded from 18.06.3-ce to 19.03.5
• git upgraded from 2.20.1 to 2.25.0

Improvements

• You can now configure the jumpbox job on an instance_group with a docker job on it to colocate users with SSH keys. When those users SSH into the VM, they will be dumped into a docker container built specifically for them, per their requirements (of tooling, OS, env, etc.).

• Containers are now properly shut down, via docker-compose and a follow-up docker stop on any stragglers, to ensure that if a process had a volume open, that it would relinquish that control after a monit stop.

  The side-effect of this is that if you stop and (re)start the docker monit job manually, on-box, the post-start script doesn't run and you don't get back your compose'd containers. A simple fix is to manually trigger the post-start yourself.

  If, however, you bosh stop / bosh start (from off-box), everything works, since BOSH knows to trigger the post-start for you.

• Normally, one ought to specify a YAML file for ttar (via the files property) as a string of YAML, embedded in a BOSH YAML manifest. However, it makes sense, especially with Spruce's (( vault ... )) and (( file ... )) operators, or ((credhub)) notation, to want to continue the YAML love into the file, and have the BOSH release render it into a string for us.