Skip to content

Releases: cloudfoundry/garden-runc-release

GRR v1.15.1

28 Jun 13:45
Compare
Choose a tag to compare
  • Adds additional masked directory paths for defense-in-depth
  • Fixes some possible leaks in error cases for processes with a custom image

GRR v1.15.0: Containerd Your Enthusiasm

18 Jun 09:36
Compare
Choose a tag to compare

GRR v1.14.0: Veni, Vidi, Vendi

04 Jun 15:19
Compare
Choose a tag to compare

Minor updates

  • Log warnings from network plugin (cloudfoundry/guardian#116)
  • Tested with Xenial stemcells
  • We no longer emit the StoreUsage metric from Groot, since this had stopped meaning anything sensible and had broken tests in Xenial (cloudfoundry/grootfs@c015687)
  • Under the covers we've taken a large hacksaw to our vending strategy and tidied things up massively

GRR v1.13.3

22 May 13:16
Compare
Choose a tag to compare
  • Reverts Golang version temporarily to 1.9 (due to a bug in TLS in 1.10)
  • Adds experimental logging.format.timestamp property
  • Fixes an issue where the xfs store did not have ftype=1 set due to an old version of xfsprogs in the stemcell, causing issues with deleted files in docker images. (#77)
    • Note: this fix will only apply after a recreate/new stemcell is deployed, we recommend users of docker image-based containers perform a bosh recreate or deploy with a new stemcell to get this fix

GRR v1.13.2

11 May 08:59
Compare
Choose a tag to compare
  • Fixes a bug where the deprecated graph_cleanup_threshold_in_mb property (which should still be respected if set to a value other than -1), was not respected if set to 0
  • Adds an option to explicitly disable swap limits (NOTE: please only use this if swap is disabled in the kernel) #73

GRR v1.13.1

25 Apr 21:25
Compare
Choose a tag to compare
  • Fixes a regression around bind mounts in v1.13

1.13.0 - Please don't use this release.

11 Apr 20:56
Compare
Choose a tag to compare

Please don't use this release. It introduces a bug in bind mounts that is likely to cause problems for most clients. Expect a patch release very soon. Apologies for the inconvenience!

  • Fixes for CVE-2018-1277
  • Fixes for Grootfs startup issues in slower environments
  • Pids.max and Pids.nr are now reported in Metrics

GRR v1.12.1: Someone needs a timeout

15 Mar 15:27
Compare
Choose a tag to compare

Sets a more generous monit timeout (2 minutes) since the startup script could sometimes fail to complete in the default 30 seconds on slow environments

GRR v1.12.0: Don't Quota Me On This

12 Mar 10:52
Compare
Choose a tag to compare

Lots of good stuff in this release, unless you really love trying to guess the right number to set garbage collection thresholds to:

Better Garbage Collection!

Garbage collection of root filesystem layers:

  • Now bases the collection threshold on actual downloaded layer sizes plus reserved disk quotas (i.e. it accounts for the maximum amount of actually-used space in the grootfs store).
  • Sensibly defaults to the size of the data disk minus a reserved amount for other jobs in the same cell (15GB, by default). If this is lower than the disk size then we run garbage collection on every create, which is the Right Thing To Do in this case (being over threshold does not cause creates to fail, it just causes GC to run).
  • Should not require operator interaction to do the Right Thing
  • Has lots more documentation here.

Action Required For Existing Consumers: If you are manually setting graph_cleanup_threshold_in_mb you should remove this property to allow garden to calculate the threshold for you. If you would like to specify a different amount of reserved space for other jobs, you can set grootfs.reserved_space_for_other_jobs_in_mb.

Image Management Improvements

  • Layers with Opaque Whiteouts are now properly supported. This previously caused a small number of docker images to have empty directories which should not have been empty.
  • Grootfs is now used by default in the standalone gdn binary
  • Layer sizes are now properly validated in all places
  • Fixed support for Azure docker image repositories

Miscellaneous Good Things

  • Processes with their own Image and the OverrideContainerLimits field specified can now override cpu and memory limits
  • Removed the AllowNetworks property since it never worked (setting it will continue to do nothing, as before- but at least we no longer advertise a property that doesn't do anything)
  • Ensured GraceTime works for existing connections (#58)
  • Richer errors when a process fails to launch due to the requested binary not being present in the container (useful for e.g. falling back from bash to sh)

GRR v1.11.1: This One Goes To 11.1

30 Jan 17:02
Compare
Choose a tag to compare

This one..