897dd2839a
We only want to copy our own rpmdb to the base rpmdb location in the server-side paths. OTOH, when creating layered commits client-side, we want to make sure that we *don't* touch the base rpmdb location. Accordingly, move the logic that does the hardlinking into `postprocess_final`. This can cause issues if we want to make use of the base rpmdb (as in a forthcoming patch) of commits that were not created by a recent enough rpm-ostree which inject the base rpmdb. When layering on such base commits, we would unwittingly copy the new rpmdb (with the layered packages) into the base rpmdb location. This then of course throws off any logic that assumes the rpmdb at that location is from the base layer. There's a slight compatibility issue here: there are still older layered commits out there where we did this and which might throw off new logic that relies on this. We bump the clientlayer version so that we can just check for that version to know whether it's safe to use the base rpmdb. Closes: #1560 Approved by: cgwalters |
||
|---|---|---|
| .github | ||
| api-doc | ||
| buildutil | ||
| ci | ||
| design | ||
| docs | ||
| experiments-and-demos/skopeo2ostree | ||
| libdnf@7ecb2f5ddc | ||
| libglnx@470af8763f | ||
| man | ||
| packaging | ||
| rust | ||
| 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 | ||
| Vagrantfile | ||
rpm-ostree: A true hybrid image/package system
rpm-ostree combines libostree (an image system), with libdnf (a package system), bringing many of the benefits of both together.
+-----------------------------------------+
| |
| rpm-ostree (daemon + CLI) |
+------> <---------+
| | status, upgrade, rollback, | |
| | pkg layering, initramfs --enable | |
| | | |
| +-----------------------------------------+ |
| |
| |
| |
+-----------------|-------------------------+ +-----------------------|-----------------+
| | | |
| libostree (image system) | | libdnf (pkg system) |
| | | |
| C API, hardlink fs trees, system repo, | | ties together libsolv (SAT solver) |
| commits, atomic bootloader swap | | with librepo (RPM repo downloads) |
| | | |
+-------------------------------------------+ +-----------------------------------------+
For more information, see the online manual: Read The Docs (rpm-ostree)
Features:
- Transactional, background image-based (versioned/checksummed) upgrades
- OS rollback without affecting user data (
/usrbut not/etc,/var) via libostree - Client-side package layering (and overrides)
- Easily make your own:
rpm-ostree compose tree
Projects using rpm-ostree
Project Atomic is an umbrella project for delivering upstream container technologies and combined with a minimized, atomically upgradable host system to Fedora, Red Hat Enterprise Linux, and CentOS.
rpm-ostree is the underlying technology for host updates. The headlining project is "Atomic Host", which is a server variant oriented towards running Linux containers using e.g. Kubernetes. However, there is now also a Workstation variant, showing the full generality of the rpm-ostree model.
Manual
For more information, see the online manual: Read The Docs (rpm-ostree)
Talks and media
A number of Project Atomic talks are available; see for example this post which has a bigger collection that also includes talks on containers.
rpm-ostree specific talks:
- devconf.cz 2018: Colin Walters: Hybrid image/package OS updates with rpm-ostree slides
- devconf.cz 2018: Peter Robinson: Using Fedora and OSTree for IoT