v0.3.2

This release introduces much improved documentation and a few new features.

The highlight of this release is that Rocket can now natively run Docker
images. To do this, it leverages the appc/docker2aci library which performs a
straightforward conversion betwen images in the Docker format and the appc
format.

A simple example:

	$ rkt --insecure-skip-verify run docker://redis docker://tenstartups/redis-commander
	rkt: fetching image from docker://redis
	rkt: warning: signature verification has been disabled
	Downloading layer: 511136ea3c5a64f264b78b5433614aec563103b4d4702f3ba7d4d2698e22c158
	...

Note that since Docker images do not support image signature verifications, the
`-insecure-skip-verify` must be used.

Another important change in this release is that the default location for the
stage1 image used by `rkt run` can now be set at build time, by setting the
`RKT_STAGE1_IMAGE` environment variable when invoking the build script. (If
this is not set, `rkt run` will continue with its previous behaviour of looking
for a stage1.aci in the same directory as the binary itself. This makes it
easier for distributions to package Rocket and include the stage1 wherever
they choose (for example, `/usr/lib/rkt/stage1.aci`). For more information, see
rkt#520

v0.3.1

The primary motivation for this release is to resynchronise versions with the appc spec. To minimise confusion in the short term we intend to keep the major/minor version of Rocket aligned with the version of spec it implements; hence, since yesterday v0.3.0 of the appc spec was released, today Rocket becomes v0.3.1. After the spec (and Rocket) reach v1.0.0, we may relax this restriction.

This release also resolves an upstream bug in the appc discovery code which was causing rkt trust to fail in certain cases.

v0.3.0

This release includes two new commands:
- `rkt trust` can be used to discover and trust public keys for image signatures
- `rkt list` can list Rocket containers on a system

Internally there are two significant changes to the build process:
- the specification (appc/spec) is now vendored
- stage1 is no longer embedded using go-bindata. Instead, Rocket will consume
an ACI for its stage1, which makes it much easier to swap in alternative stage1
images.

v0.2.0

This introduces countless features and improvements over v0.1.1. Highlights include several new commands (`rkt status`, `rkt enter`, `rkt gc`) and signature validation.

v0.1.1

The most significant change in this release is that the spec has been split into its own repository (https://github.com/appc/spec), and significantly updated since the last release - so many of the changes were to update to match the latest spec.

Numerous improvements and fixes over v0.1.0:
- Rocket builds on non-Linux (in a limited capacity)
- Fix bug handling uncompressed images
- More efficient image handling in CAS
- mkrootfs now caches and GPG checks images
- stage1 is now properly decoupled from host runtime
- stage1 supports socket activation
- stage1 no longer warns about timezones
- cas now logs download progress to stdout
- rkt run now acquires an exclusive lock on the container directory and records the PID of the process

v0.1.0

- tons of documentation improvements added
- actool introduced along with documentation
- image discovery introduced to rkt run and rkt fetch

stage0: bundle stage1 rootfs and init binaries into rkt exe

 This also runs mkrootfs.sh if necessary