containers/bootc
1
0
Fork 0
mirror of https://github.com/containers/bootc.git synced 2026-02-05 15:45:53 +01:00
Code Issues Activity
Files
actions/update-generated-files
bootc/hack/Containerfile

22 lines
773 B
Docker
Raw Permalink Normal View History

build-sys: Rework to have toplevel Dockerfile + Justfile This is aligning with what I did in https://github.com/ostreedev/ostree/pull/3439 - What gets invoked in e.g. GHA should ideally most be `just` commands that are easy to run locally too (with sudo in GHA, without sudo locally) - Move the "core build" to the toplevel so that one can just `podman build` directly too (without the Justfile) and have it do something useful - The "always build and test in a container" helps for LLM-assisted coding because what they can do is inherently sandboxed Signed-off-by: Colin Walters <walters@verbum.org>
2025-06-06 11:11:58 -04:00
# This injects some extra testing stuff into our image
hack: Rework+cleanup container build Main motivation: I was looking at making more changes here - Use an idiom I'd like to standardize more of copy context to `FROM scratch` image which is then mounted and consumed in other phases by mounting. This helps avoid polluting later containers with intermediate copied files. - Change `build.sh` to handle being run from any directory - Drop the `dev-rootfs` stuff as it's weird and awkward; instead we should encourage multi-step builds deriving from this image - Don't make `bootc.tar.zst` only to immediately untar it; just use `COPY` from the build container - Use heredocs to condense multiple `RUN` invocations to avoid pointless small layers Signed-off-by: Colin Walters <walters@verbum.org>
2025-05-02 10:56:01 -04:00
FROM scratch as context
# We only need this stuff in the initial context
COPY hack /hack
build.sh: Use our embedded spec One CI run just got a server error fetching the spec from Fedora. We have a spec here (which I don't like but we do) so use it to lower CI flakes. Signed-off-by: Colin Walters <walters@verbum.org>
2025-01-17 09:54:35 -05:00
COPY contrib /contrib
hack: Rework+cleanup container build Main motivation: I was looking at making more changes here - Use an idiom I'd like to standardize more of copy context to `FROM scratch` image which is then mounted and consumed in other phases by mounting. This helps avoid polluting later containers with intermediate copied files. - Change `build.sh` to handle being run from any directory - Drop the `dev-rootfs` stuff as it's weird and awkward; instead we should encourage multi-step builds deriving from this image - Don't make `bootc.tar.zst` only to immediately untar it; just use `COPY` from the build container - Use heredocs to condense multiple `RUN` invocations to avoid pointless small layers Signed-off-by: Colin Walters <walters@verbum.org>
2025-05-02 10:56:01 -04:00
build-sys: Rework to have toplevel Dockerfile + Justfile This is aligning with what I did in https://github.com/ostreedev/ostree/pull/3439 - What gets invoked in e.g. GHA should ideally most be `just` commands that are easy to run locally too (with sudo in GHA, without sudo locally) - Move the "core build" to the toplevel so that one can just `podman build` directly too (without the Justfile) and have it do something useful - The "always build and test in a container" helps for LLM-assisted coding because what they can do is inherently sandboxed Signed-off-by: Colin Walters <walters@verbum.org>
2025-06-06 11:11:58 -04:00
FROM localhost/bootc
install: Fix install config kargs + to-filesystem I think this got broken in a refactoring; add test coverage. In general all the heavy lifting should move out of `baseline.rs`; a good way to do that is probably to take the next step of making it its own crate that doesn't depend on the bootc core logic perhaps. Closes: https://github.com/containers/bootc/issues/570 Signed-off-by: Colin Walters <walters@verbum.org>
2024-06-16 12:10:00 +00:00
# We support e.g. adding cloud-init
hack: Add support for installing cloud-init+rsync These are things that https://tmt.readthedocs.io/en/stable/ wants, and the goal is to support running under tmt more directly. Part of https://github.com/containers/bootc/issues/543 With this I can run: ``` provision: how: virtual image: /home/walters/src/github/containers/bootc/target/testbootc-cloud.qcow2 summary: Basic smoke test execute: how: tmt script: bootc status ``` Signed-off-by: Colin Walters <walters@verbum.org>
2024-06-09 10:17:55 -04:00
ARG variant=
hack: Rework+cleanup container build Main motivation: I was looking at making more changes here - Use an idiom I'd like to standardize more of copy context to `FROM scratch` image which is then mounted and consumed in other phases by mounting. This helps avoid polluting later containers with intermediate copied files. - Change `build.sh` to handle being run from any directory - Drop the `dev-rootfs` stuff as it's weird and awkward; instead we should encourage multi-step builds deriving from this image - Don't make `bootc.tar.zst` only to immediately untar it; just use `COPY` from the build container - Use heredocs to condense multiple `RUN` invocations to avoid pointless small layers Signed-off-by: Colin Walters <walters@verbum.org>
2025-05-02 10:56:01 -04:00
# And this layer has additional stuff for testing, such as nushell etc.
RUN --mount=type=bind,from=context,target=/run/context <<EORUN
set -xeuo pipefail
/run/context/hack/provision-derived.sh "$variant"
# Add some testing kargs into our dev builds
install -D -t /usr/lib/bootc/kargs.d /run/context/hack/test-kargs/*
install: Fix install config kargs + to-filesystem I think this got broken in a refactoring; add test coverage. In general all the heavy lifting should move out of `baseline.rs`; a good way to do that is probably to take the next step of making it its own crate that doesn't depend on the bootc core logic perhaps. Closes: https://github.com/containers/bootc/issues/570 Signed-off-by: Colin Walters <walters@verbum.org>
2024-06-16 12:10:00 +00:00
# Also copy in some default install configs we use for testing
hack: Rework+cleanup container build Main motivation: I was looking at making more changes here - Use an idiom I'd like to standardize more of copy context to `FROM scratch` image which is then mounted and consumed in other phases by mounting. This helps avoid polluting later containers with intermediate copied files. - Change `build.sh` to handle being run from any directory - Drop the `dev-rootfs` stuff as it's weird and awkward; instead we should encourage multi-step builds deriving from this image - Don't make `bootc.tar.zst` only to immediately untar it; just use `COPY` from the build container - Use heredocs to condense multiple `RUN` invocations to avoid pointless small layers Signed-off-by: Colin Walters <walters@verbum.org>
2025-05-02 10:56:01 -04:00
install -D -t /usr/lib/bootc/install/ /run/context/hack/install-test-configs/*
# Finally, test our own linting
bootc container lint --fatal-warnings
EORUN
Copy Permalink