Skip to content

Releases: cloudfoundry/grootfs

0.17.1

04 May 16:09
Compare
Choose a tag to compare

...this patch release:

  • Improves the performance of the graph cleanup store measuring operation.
  • Sets the BOSH release Dropsonde port to 3457.
  • Changes grootfs delete in order to not corrupt the store when it deletes a half-created image.

0.17.0

12 Apr 10:01
Compare
Choose a tag to compare
  • Enhanced metrics: https://github.com/cloudfoundry/grootfs#metrics.
  • New BOSH release property: grootfs.skip_mount.
  • grootfs create JSON output:
    • Added a boolean BOSH release property named grootfs.json_output to make grootfs create calls return JSON.
    • This property will be removed in the next releases. grootfs create will only return JSON output.

v0.16.0

05 Apr 10:48
Compare
Choose a tag to compare

Updating GrootFS to v0.16.0, if running with GrootFS already, will require recreating the Diego cells.

  • grootfs create can now, optionally, return a JSON object instead of a rootfs path. Use --json or create.json to enable this feature. This feature flag will soon be removed and JSON output will be the default behaviour.
  • grootfs create can now, optionally, not mount the final container filesystem. Use --without-mount or create.without_mount to enable this feature.
  • Fix: Pull images with opaque whiteouts while using user-mappings and run by root.

Overlay-XFS filesystem driver

  • Support images with more than 40 layers.
  • Rootless create of local tar-ball-based images without disk quotas.

BTRFS filesystem driver

  • Pull images with opaque whiteouts while using user-mappings and run by a non-root user.
  • Delete BTRFS subvolumes created in the container before deleting the image.

init-store/delete-store work

  • grootfs init-store can create a store based on an existing and mounted BTRFS/XFS filesystem.
  • grootfs init-store receives --uid-mapping/--gid-mapping flags and infers store owner and group using them.
  • grootfs delete-store can delete a store, without deleting the backing filesystem.

0.15.0

10 Mar 16:52
Compare
Choose a tag to compare
  • Do not leak corrupted volumes when GrootFS is killed half-way during a grootfs create.
  • Uses a more user-friendly error in grootfs delete when the image is not found.
  • Apply a consistent configuration file options naming convention.
  • Remove the need of passing --xfs-progs to grootfs stats in the overlay-xfs driver.
  • Allow newer layers to overwrite existing files with symlinks.
  • Always create the whiteout device when using the overlay-xfs driver.

Fix some regressions and cf-deployment-ready

01 Mar 13:49
Compare
Choose a tag to compare
  • Fix: grootfs clean issue on a Overlay-XFS store, when using disk quotas.
  • Fix: grootfs create issue on a BTRFS store, when running as a non-root user.
  • Return error when the requested filesystem driver is unsupported.
  • Add BOSH CLI ops-file for the cf-deployment.

Docker support in overlay-xfs driver

24 Feb 11:42
Compare
Choose a tag to compare
  • Stats doesn't fail when using overlay+xfs with no limits
  • Fix whiteout implementation for overlay+xfs driver
  • Support inclusive quotas for Overlay-XFS

The overlay-xfs filesystem driver can be used in Cloud Foundry

20 Feb 18:04
Compare
Choose a tag to compare
  • Only with tar-based images at the moment.

v0.11.0 - Basic support for the overlay-xfs filesystem driver

16 Feb 12:32
Compare
Choose a tag to compare
Change image internal dirs permissions to 0755

* Users != store owner were unable to run any process in the container
  due to wrong permissions (was 0700)

[#139824231]

Signed-off-by: Claudia Beresford <cberesford@pivotal.io>

0.10.0

16 Feb 12:31
Compare
Choose a tag to compare
Fix test compilation after conflict

[#138265057]

0.9.0

27 Jan 19:11
Compare
Choose a tag to compare
  • Temporary blob files are now created inside the store (instead of the $TEMP directory).