garden-linux/0.326.0

Once again, a bug in our pipeline caused the version number to be bumped multiple times. Now fixed, so this should be the last time.

matching garden sha: 82ff031e787b461f85791f654938e631970f87ad - Switched from btrfs to aufs due to performance issues under load when using btrfs disk quotas - As part of this, we’ve temporarily disabled disk usage reporting and graph cleanup - Disk quotas may now only be provided only at container creation time (i.e. the LimitDisk call is now a no-op and will likely be removed in a future release) - The Total disk limit scope doesn’t work yet - Added additional logging around iptables setup, container listing, and disk related activities - Minor improvements to container creation speed

Important Notes: - If garden is being run in a container, it may be necessary to modprobe aufs on the host if the aufs kernel module has not already been loaded (because garden cannot dynamically load this inside a container). This is a temporary workaround until all environments are using the latest version of garden (the latest versions of garden will do this automatically as long as the outermost garden is running the latest version). - AUFS requires that the graph directory supplied to garden is not already using aufs, overlayfs or btrfs. This may be the case if running garden inside garden. In this case it may be necessary to mount tmpfs or a loop device formatted with ext4 over the graph directory to allow aufs to be used. - Snapshotting won’t work when upgrading to this release from an older release that used btrfs - You should recreate any machines that are running Garden-Linux when upgrading to this release. Failure to do this may prevent deletion of existing containers, or cause other unexpected issues.