Repository navigation
Tags
Tags
rkt 0.5.6 includes better integration with systemd on the host, some … …minor bug fixes and a new ipvlan network plugin. - Updated to v0.5.2 of the appc spec - support running from systemd unit files for top-level isolation - support per-app logging via journalctl. This is only supported if stage1 has systemd v219 or v220 - add ipvlan network plugin - new rkt subcommand: cat-manifest - extract ACI in a chroot to avoid malformed links modifying the host filesystem - improve rkt error message if the user doesn’t provide required volumes - fix rkt status when using overlayfs - support for some arm architectures - documentation improvements
v0.5.4 - added configuration support for repository authentication (HTTP Basic Auth, O Auth, and Docker repositories). Full details in Documentation/ 10A15 configuration.md - `rkt run` now supports per-app arguments and per-image `--signature` specifications - `rkt run` and `rkt fetch` will now verify signatures for local image files - `rkt run` with `--private-net` now supports port forwarding (using `--port=NAME:1234`) - `rkt run` now supports a `--local` flag to use only local images (i.e. no discovery or remote image retrieval will be performed) - added initial support for running directly from a pod manifest - the store DB now supports migrations for future versions - systemd-nspawn machine names are now set to pod UUID - removed the `--spawn-metadata-svc` option from `rkt run`; this mode was inherently racy and really only for convenience. A separate `rkt metadata-service` invocation should be used instead. - various internal codebase refactoring: "cas" renamed to "store", tasks to encapsulate image fetch operations, etc - bumped docker2aci to support authentication for Docker registries and fix a bug when retrieving images from Google Container Registry - fixed a bug where `--interactive` did not work with arguments - garbage collection for networking is now embedded in the stage1 image - when rendering images into the treestore, a global syncfs() is used instead of a per-file sync(). This should significantly improve performance when first extracting large images - added extensive functional testing on semaphoreci.com/coreos/rkt - added a test-auth-server to facilitate testing of fetching images
v0.5.3
Minor updates over v0.5.2, finalising the move to pods in the latest appc spec
- {Container,container} changed globally to {Pod,pod}
- {Rocket,rocket} changed globally to `rkt`
- `rkt install` properly sets permissions for all directories
- `rkt fetch` leverages the cas.Store TmpDir/TmpFile functions (now exported) to generate temporary files for downloads
- Pod lifecycle states are now exported for use by other packages
- Metadata service properly synchronizes access to pod state
This release is a minor update over v0.5.1, incorporating several bug… … fixes and a couple of small new features: - `rkt enter` works when overlayfs is not available - `rkt run` now supports the `--no-overlay` option referenced (but not implemented!) in the previous release - the appc-specified environment variables (PATH, HOME, etc) are once again set correctly during `rkt run` - metadata-service no longer manipulates IP tables rules as it connects over a unix socket by default - pkg/lock has been improved to also support regular (non-directory) files - images in the cas are now locked at runtime (as described in rkt#460)
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
PreviousNext