@iaguis iaguis released this Feb 4, 2016 · 2254 commits to master since this release

Assets 4

This marks the first release of rkt recommended for use in production.
The command-line UX and on-disk format are considered stable and safe to develop against.
Any changes to these interfaces will be backwards compatible and subject to formal deprecation.
The API is not yet completely stabilized, but is functional and suitable for use by early adopters.

For those new to rkt, we have a blog post explaining out how to get started with 1.0

Also check out the landing page on the CoreOS site for more information.

New features and UX changes

  • Add pod creation and start times to rkt list and rkt status (#2030). See rkt list and rkt status documentation.
  • The DNS configuration can now be passed to the pod via the command line (#2040). See DNS support documentation.
  • Errors are now structured, allowing for better control of the output (#1937). See Error & Output for how a developer should use it.
  • All output now uses the new log package in pkg/log to provide a more clean and consistent output format and more helpful debug output (#1937).
  • Added configuration for stage1 image. Users can drop a configuration file to /etc/rkt/stage1.d (or to stage1.d in the user configuration directory) to tell rkt to use a different stage1 image name, version and location instead of build-time defaults (#1977).
  • Replaced the --stage1-image flag with a new set of flags. --stage1-url, --stage-path, --stage1-name do the usual fetching from remote if the image does not exist in the store. --stage1-hash takes the stage1 image directly from the store. --stage1-from-dir works together with the default stage1 images directory and is described in the next point (#1977).
  • Added default stage1 images directory. User can use the newly added --stage1-from-dir parameter to avoid typing the full path. --stage1-from-dir behaves like --stage1-path (#1977).
  • Removed the deprecated --insecure-skip-verify flag (#2068).
  • Fetched keys are no longer automatically trusted by default, unless --trust-keys-from-https is used. Additionally, newly fetched keys have to be explicitly trusted with rkt trust if a previous key was trusted for the same image prefix (#2033).
  • Use NAT loopback to make ports forwarded in pods accessible from localhost (#1256).
  • Show a clearer error message when unprivileged users execute commands that require root privileges (#2081).
  • Add a rkt tmpfiles configuration file to make the creation of the rkt data directory on first boot easier (#2088).
  • Remove rkt install command. It was replaced with a setup-data-dir.sh script (#2101.

Bug fixes

  • Fix regression when authenticating to v2 Docker registries (#2008).
  • Don't link to libacl, but dlopen it (#1963). This means that rkt will not crash if libacl is not present on the host, but it will just print a warning.
  • Only suppress diagnostic messages, not error messages in stage1 (#2111).

Other changes

  • Trusted Platform Module logging (TPM) is now enabled by default (#1815). This ensures that rkt benefits from security features by default. See rkt's Build Configuration documentation.
  • Added long descriptions to all rkt commands (#2098).


  • The --stage1-image flag was removed. Scripts using it should be updated to use one of --stage1-url, --stage1-path, --stage1-name, --stage1-hash or --stage1-from-dir
  • All uses of the deprecated --insecure-skip-verify flag should be replaced with the --insecure-options flag which allows user to selectively disable security features.
  • The rkt install command was removed in favor of the dist/scripts/setup-data-dir.sh script.

Note for packagers

With this release, rkt RPM/dpkg packages should have the following updates:

  • Pass --enable-tpm=no to configure script, if rkt should not use TPM.
  • Use the --with-default-stage1-images-directory configure flag, if the default is not acceptable and install the built stage1 images there.
  • Distributions using systemd: install the new file dist/init/systemd/tmpfiles.d/rkt.conf in /usr/lib/tmpfiles.d/rkt.conf and then run systemd-tmpfiles --create rkt.conf. This can replace running rkt install to set the correct ownership and permissions.