f255fba09f
Verifying the systemd unit also checks if any referred systemd units (Wants, Requires, After) exist and if all commands in Exec exist and are executable. Without '--root', the systemd-analyze verify command is testing this against files in the build root, which isn't valid. Units and binaries might not exist in the build root when referenced in the image root tree, making the unit fail when when it's valid. Conversely, the verification can succeed by finding executables in the build root that don't exist in the image root tree when it should be failing. When verifying user units, systemd expects runtime directories. All of this makes it quite difficult to verify systemd units properly when building an image. The call is useful for making sure the unit is structured properly, but the user unit verification setup is difficult to accomplish in a general way while building. Remove the systemd-analyze verify step from the stage. Move it to the unit test so that we have some assurance that our unit file structure is correct and things work as expected. Create referenced unit files and commands to make the unit valid. |
||
|---|---|---|
| .devcontainer | ||
| .github | ||
| assemblers | ||
| data | ||
| devices | ||
| docs | ||
| inputs | ||
| mounts | ||
| osbuild | ||
| runners | ||
| schemas | ||
| schutzbot | ||
| selinux | ||
| sources | ||
| stages | ||
| test | ||
| tools | ||
| .bandit | ||
| .editorconfig | ||
| .git-blame-ignore-revs | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| .mypy.ini | ||
| .packit.yaml | ||
| .ruff.toml | ||
| LICENSE | ||
| Makefile | ||
| osbuild.spec | ||
| README.md | ||
| requirements.txt | ||
| samples | ||
| Schutzfile | ||
| setup.cfg | ||
| setup.py | ||
| tox.ini | ||
OSBuild
Build-Pipelines for Operating System Artifacts
OSBuild is a pipeline-based build system for operating system artifacts. It defines a universal pipeline description and a build system to execute them, producing artifacts like operating system images, working towards an image build pipeline that is more comprehensible, reproducible, and extendable.
See the osbuild(1) man-page for details on how to run osbuild, the definition
of the pipeline description, and more.
Project
- Website: https://www.osbuild.org
- Bug Tracker: https://github.com/osbuild/osbuild/issues
- Matrix: #image-builder on fedoraproject.org
- Mailing List: image-builder@redhat.com
- Changelog: https://github.com/osbuild/osbuild/releases
Principles
- OSBuild stages are never broken, only deprecated. The same manifest should always produce the same output.
- OSBuild stages should be explicit whenever possible instead of e.g. relying on the state of the tree.
- Pipelines are independent, so the tree is expected to be empty at the beginning of each.
- Manifests are expected to be machine-generated, so OSBuild has no convenience functions to support manually created manifests.
- The build environment is confined against accidental misuse, but this should not be considered a security boundary.
- OSBuild may only use Python language features supported by the oldest target distribution.
Contributing
Please refer to the developer guide to learn about our workflow, code style and more.
Requirements
The requirements for this project are:
bubblewrap >= 0.4.0python >= 3.6
Additionally, the built-in stages require:
bash >= 5.0coreutils >= 8.31curl >= 7.68qemu-img >= 4.2.0rpm >= 4.15tar >= 1.32util-linux >= 235skopeo
At build-time, the following software is required:
python-docutils >= 0.13pkg-config >= 0.29
Testing requires additional software:
pytest
Build
Osbuild is a python script so it is not compiled. To verify changes made to the code use included makefile rules:
make lintto run linter on top of the codemake test-allto run base set of testssudo make test-runto run extended set of tests (takes long time)
Installation
Installing osbuild requires to not only install the osbuild module, but also
additional artifacts such as tools (i.e: osbuild-mpp) sources, stages, schemas
and SELinux policies.
For this reason, doing an installation from source is not trivial and the easier way to install it is to create the set of RPMs that contain all these components.
This can be done with the rpm make target, i.e:
make rpm
A set of RPMs will be created in the ./rpmbuild/RPMS/noarch/ directory and can
be installed in the system using the distribution package manager, i.e:
sudo dnf install ./rpmbuild/RPMS/noarch/*.rpm
Repository
- web: https://github.com/osbuild/osbuild
- https:
https://github.com/osbuild/osbuild.git - ssh:
git@github.com:osbuild/osbuild.git
License
- Apache-2.0
- See LICENSE file for details.