Repository navigation
Tags
Tags
v0.5.1 This release updates Rocket to follow the latest version of the appc spec, v0.5.1. This involves the major change of moving to _pods_ and _Pod Manifests_ (which enhance and supplant the previous _Container Runtime Manifest_). The Rocket codebase has been updated across the board to reflect the schema/spec change, as well as changing various terminology in other human-readable places: for example, the previous ambiguous (unqualified) "container" is now replaced everywhere with "pod". This release also introduces a number of key features and minor changes: - overlayfs support, enabled for `rkt run` by default (disable with `--no-overlayfs`) - to facilitate overlayfs, the CAS now features a tree store which stores expanded versions of images - the default stage1 (based on systemd) can now be built from source, instead of only derived from an existing binary distribution as previously. This is configurable using the new `RKT_STAGE1_USR_FROM` environment variable when invoking the build script - see fdcd649 - the metadata service now uses a Unix socket for registration; this limits who can register/unregister pods by leveraging filesystem permissions on the socket - `rkt list` now abbreviates UUIDs by default (configurable with `--full`) - the ImageManifest's `readOnly` field (for volume mounts) is now overridden by the rkt command line - a simple debug script (in scripts/debug) to facilitate easier debugging of applications running under Rocket by injecting Busybox into the pod - documentation for the metadata service, as well as example systemd unit files
v0.4.2 - Add container IP address information to `rkt list` - Provide `/sys` and `/dev/shm` to apps (per spec) - Introduce "latest" pattern handling for local image index - Implement FIFO support in tar package - First support for interactive containers. This is currently only supported if a container has one app. - Restore atime and mtime during tar extraction - Bump docker2aci dependency
v0.4.0 - Updated to v0.4.0 of the appc spec - Introduced a database for indexing local images in the CAS (based on github.com/cznic/ql) - Refactored container lifecycle to support a new "prepared" state, to pre-allocate a container UUID without immediately running the application - Added support for passing arguments to apps through the `rkt run` CLI - Implemented ACI rendering for dependencies - Renamed `rkt metadatasvc` -> `rkt metadata-service` - Added documentation around networking, container lifecycle, and rkt commands
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.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 a 533E bout 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
PreviousNext