toolbox/playbooks
Debarshi Ray de652f4102 Test that toolbox(1) can be built without podman(1) and subordinate IDs
This is meant to roughly replicate the build environments used by
downstream distributors to build toolbox(1).  These can be restricted in
odd ways compared to a fully featured environment where toolbox(1) is
actually going to be used.  eg., the inability to use podman(1) in the
case of Fedora or not having subordinate user and group ID ranges in the
case of openSUSE.

It's important to ensure that toolbox(1) can be built by downstream
distributors without any unnecessary hassle.

https://github.com/containers/podman/issues/17657
https://github.com/containers/toolbox/issues/1246
2023-03-02 10:25:54 +01:00
..
build.yaml .zuul, playbooks: Add copyright and license notices 2022-11-28 22:47:15 +01:00
dependencies-centos-9-stream.yaml Fix spelling mistakes 2023-01-31 15:53:15 +01:00
dependencies-fedora-restricted.yaml Test that toolbox(1) can be built without podman(1) and subordinate IDs 2023-03-02 10:25:54 +01:00
dependencies-fedora.yaml Fix spelling mistakes 2023-01-31 15:53:15 +01:00
setup-env-migration-path-for-coreos-toolbox.yaml Test -Dmigration_path_for_coreos_toolbox on CentOS Stream 9 2022-12-14 23:09:55 +01:00
setup-env-restricted.yaml Test that toolbox(1) can be built without podman(1) and subordinate IDs 2023-03-02 10:25:54 +01:00
setup-env.yaml playbooks: Rename the file with the dependencies 2022-12-14 23:09:55 +01:00
system-test.yaml .zuul, playbooks: Add copyright and license notices 2022-11-28 22:47:15 +01:00
unit-test.yaml playbooks: Reveal the standard error & output streams from 'meson test' 2022-12-14 23:09:55 +01:00