-
Notifications
You must be signed in to change notification settings - Fork 170
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: coreos/coreos-assembler
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: 3c6feeb1f1b16ad27e357c055f52f93d51684fd4
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: coreos/coreos-assembler
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: e2c27099454f8e0029a4b51b492536bd133b1bca
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 3 commits
- 2 files changed
- 1 contributor
Commits on Mar 17, 2025
-
cmd-remote-build-container: add --git-containerfile
For building the extensions, we need to be able to point buildah at the root of the git repo for the context dir but the Dockerfile in the `extensions/` subdirectory. Add a `--git-containerfile` for this.
Configuration menu - View commit details
-
Copy full SHA for cdcc9eb - Browse repository at this point
Copy the full SHA cdcc9ebView commit details -
cmd-remote-build-container: initialize submodules in git clone
When cloning the git repo to pass to buildah, make sure to initiatlize submodules. E.g. building the extensions container requires parsing the manifest, which references bits in the fedora-coreos-config submodule.
Configuration menu - View commit details
-
Copy full SHA for 1cdb8e4 - Browse repository at this point
Copy the full SHA 1cdb8e4View commit details -
lib/container_manifest: check for image before manifest
There's an asymmetry between `podman image exists` and `podman manifest exists`. The first will return 1 if the image is a manifest. The second will return 125 if the image is _not_ a manifest. I think this is probably a bug in podman, but for now we can work around this by reverting the order in which we do the checking. That way, if the image exists but isn't a manifest, we'll return `True` and not actually call `podman manifest exists` on it.
Configuration menu - View commit details
-
Copy full SHA for e2c2709 - Browse repository at this point
Copy the full SHA e2c2709View commit details
There are no files selected for viewing