Skip to content


You can find the source of this version on GitHub at cloudfoundry/diego-release. It was created based on the commit deb51e25.

Release Notes

Changes from v0.1439.0 to v0.1440.0

Important changes

The recommended version of garden-linux-release, v0.326.0, has changed its backing layer system to use aufs instead of btrfs. Please see the notes for this Garden-Linux final release for more details.

If you are upgrading from garden-linux-release v0.316.0 or earlier, we recommend you recreate your Diego Cells during the upgrade to v0.326.0 and later, to avoid issues with residual containers on the btrfs volume that garden-linux will be unable to delete. You can do this intentionally with the --recreate flag on bosh deploy, or incidentally by deploying a new stemcell at the same time. If you’ve been waiting to upgrade your stemcell, now’s a great time!

Also, if you are using the generate-deployment-manifest script to produce your Diego deployment manifest, please be aware that it has incorporated a few changes to its arguments: - The optional ‘director-uuid’ stub argument is now removed, as the BOSH director UUID will be taken from the CF manifest. - There is a new required argument that expects a stub optionally specifying the versions of the Diego, Garden-Linux, and ETCD releases to deploy. If any of these versions are missing, they will default to ‘latest’.

Other significant changes

BOSH property changes



You can reference this release in your deployment manifest from the releases section:

- name: "diego"
  version: "0.1440.0"
  url: ""
  sha1: "fbbdc3ac1fe5b48332f5703cf021d5022cbd7ca4"

Or upload it to your director with the upload-release command:

bosh upload-release --sha1 fbbdc3ac1fe5b48332f5703cf021d5022cbd7ca4 \