转载

Rocket 0.5.4 发布，CoreOS 的容器引擎

开源中国的 IT 公司开源软件整理计划介绍

Rocket 0.5.4 发布了，Rocket （也叫 rkt）是 CoreOS 推出的一款容器引擎，和 Docker 类似，帮助开发者打包应用和依赖包到可移植容器中，简化搭环境等部署工作。Rocket 和 Docker 不同的地方在于，Rocket 没有 Docker 那些为企业用户提供的“友好功能”，比如云服务加速工具、集群系统等。反过来说，Rocket 想做的，是一个更纯粹的业界标准。

Rocket 0.5.4 版本改进内容包括：

- added configuration support for repository authentication (HTTP Basic Auth, O Auth, and Docker repositories). Full details in Documentation/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

正文到此结束