mirror of https://github.com/containers/bootc.git synced 2026-02-05 15:45:53 +01:00

Files

Colin Walters fa474a9c3f install: Drop code/test uses of --security-opt

We think this is unnecessary now; part of improving
the ergonomics of `bootc install` in general, but
especially with the `to-existing-root` path.

Once this lands, at some point later then we
can also remove it from all of the documentation.
But the most safe thing is to leave it in the
docs for a bit longer.

Closes: https://github.com/containers/bootc/issues/928

Signed-off-by: Colin Walters <walters@verbum.org>

2024-12-10 10:02:12 -05:00

src

install: Drop code/test uses of --security-opt

2024-12-10 10:02:12 -05:00

Cargo.toml

fix(deps): update all dependencies

2024-10-05 11:25:16 +00:00

README.md

Move install tests shell script into Rust

2024-05-19 17:58:17 -04:00

README.md

Integration tests crate

This crate holds integration tests (as distinct from the regular Rust unit tests run as part of cargo test).

Building and running

cargo run -p tests-integration will work. Note that at the current time all test suites target an externally built bootc-compatible container image. See how things are set up in e.g. Github Actions, where we first run a podman build with the bootc git sources.

Available suites

`host-privileged`

This suite will run the target container image in a way that expects full privileges, but is not destructive.

`install-alongside`

This suite is DESTRUCTIVE, executing the bootc install to-existing-root style flow using the host root. Run it in a transient virtual machine.