d4af84d428
Switch `ex container` to `OSTREE_REPO_MODE_BARE_USER_ONLY`; this is a good match, for the same reasons as flatpak. We don't want suid binaries, we don't want to chown anything, no SELinux labeling, etc. There's no reason to write the metadata to the `BARE_USER` xattrs. The "unprivileged" context as used for `ex container` was a flag that was passed down, but I think it's a lot easier if things just infer this state by looking at whether the target repo is `bare-user-only`. Now we just have an `rpmostree_context_new_tree()` API that handles both container and compose. Closes: #1026 Approved by: jlebon
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)