31306a297b
I'm sure there is a reason for why it is the way it is, which I will learn about, but the way it is currently set up makes it hard to run commands in the target system (like `rpm -q`) without doing a chroot and doing a chroot requires some setup to happen. I guess the nice thing about the way it is prior is we get to the look at the filesystem untouched by the container runtime; which can definitely be useful for tests. |
||
|---|---|---|
| .. | ||
| cases | ||
| Dockerfile | ||
| README.md | ||
| run | ||
rootfs tests
This is a set of scripts that sanity check the target rootfs in a read-only fashion.