63af4bbdda
Right now `rpm-ostree compose tree` is very prescriptive about how things work. Trying to add anything that isn't an RPM is absolutely fighting the system. Our postprocessing system *enforces* no network access (good for reproducibilty, but still prescriptive). There's really a logical split between three phases: - install: "build a rootfs that installs packages" - postprocess: "run magical ostree postprocessing like kernel" - commit: "commit result to ostree" So there are two high level flows I'd like to enable here. First is to allow people to do *arbitrary* postprocessing between `install` and `commit`. For example, run Ansible and change `/etc`. This path basically is like what we have today with `postprocess-script.sh`, except the builder can do anything they want with network access enabled. Going much farther, this helps us support a "build with Dockerfile" style flow. We can then provide tooling to extract the container image, and combine `postprocess` and `commit`. Or completely the other way - if for example someone wants to use `rpm-ostree compose install`, they could tar up the result as a Docker/OCI image. That's now easier; an advantage of this flow over e.g. `yum --installroot` is the "change detection" code we have. Related issues/PRs: - https://github.com/projectatomic/rpm-ostree/pull/96 - https://github.com/projectatomic/rpm-ostree/issues/471 One disadvantage of this approach right now is that if one *does* go for the split approach, we lose the "input hash" metadata for example. And down the line, I'd like to add even more metadata, like the input rpm repos, which could also be rendered on the client side. But, I think we can address that later by e.g. caching the metadata in a file in the install root and picking it back up or something. Closes: #1039 Approved by: jlebon |
||
|---|---|---|
| .github | ||
| api-doc | ||
| buildutil | ||
| ci | ||
| design | ||
| docs | ||
| libdnf@022365553a | ||
| libglnx@e627524af9 | ||
| man | ||
| packaging | ||
| scripts | ||
| src | ||
| tests | ||
| vagrant | ||
| .dir-locals.el | ||
| .editorconfig | ||
| .gitmodules | ||
| .papr.yml | ||
| .vimrc | ||
| autogen.sh | ||
| configure.ac | ||
| CONTRIBUTING.md | ||
| COPYING | ||
| git.mk | ||
| HACKING.md | ||
| LICENSE | ||
| Makefile-daemon.am | ||
| Makefile-decls.am | ||
| Makefile-lib-defines.am | ||
| Makefile-lib.am | ||
| Makefile-libdnf.am | ||
| Makefile-libpriv.am | ||
| Makefile-man.am | ||
| Makefile-rpm-ostree.am | ||
| Makefile-tests.am | ||
| Makefile.am | ||
| mkdocs.yml | ||
| README.md | ||
| TODO | ||
| Vagrantfile | ||
rpm-ostree Overview
rpm-ostree is a hybrid image/package system. It uses OSTree as a base image format, and supports RPM on both the client and server side using libdnf.
For more information, see the online manual: Read The Docs (rpm-ostree)
Features:
- Atomic upgrades and rollback for host system updates
- A server side tool to consume RPMs and commit them to an OSTree repository
- A system daemon to consume OSTree commits as updates
Projects using rpm-ostree
Project Atomic uses rpm-ostree to provide a minimal host for Docker formatted Linux containers. Replicating a base immutable OS, then using Docker for applications.
Manual
For more information, see the online manual: Read The Docs (rpm-ostree)