base-images/tests/rootfs/Dockerfile

# This should always be replaced with podman build --from.
FROM localhost/image-to-test
COPY . /src
RUN /src/run /
Use rpmdb-normalize, add rootfs tests I just saw the sqlite-shm corruption in https://gitlab.com/redhat/centos-stream/containers/bootc/-/merge_requests/437#note_2372766792 so let's just go ahead and turn on rpmdb_normalize which also aids the reproducibility of the rpmdb. While we're here let's also add a long overdue "unit test" for the rootfs. This operates as a container build that mounts the container-under-test as part of a multi-stage build. Signed-off-by: Colin Walters <walters@verbum.org> 2025-02-28 09:13:06 -05:00			`# This should always be replaced with podman build --from.`
tests: simplify to use just the built bootc image 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. 2025-05-06 16:37:47 -04:00			`FROM localhost/image-to-test`
Use rpmdb-normalize, add rootfs tests I just saw the sqlite-shm corruption in https://gitlab.com/redhat/centos-stream/containers/bootc/-/merge_requests/437#note_2372766792 so let's just go ahead and turn on rpmdb_normalize which also aids the reproducibility of the rpmdb. While we're here let's also add a long overdue "unit test" for the rootfs. This operates as a container build that mounts the container-under-test as part of a multi-stage build. Signed-off-by: Colin Walters <walters@verbum.org> 2025-02-28 09:13:06 -05:00			`COPY . /src`
tests: simplify to use just the built bootc image 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. 2025-05-06 16:37:47 -04:00			`RUN /src/run /`