Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add cosa buildextend-layered #3753

Closed
wants to merge 1 commit into from

Conversation

jlebon
Copy link
Member

@jlebon jlebon commented Mar 11, 2024

As part of openshift/os#799, we'll want to
build the "OCP node" image as a layered image on top of the RHCOS base
image.

Eventually, this image should be built outside our pipelines and more
like the rest of OpenShift container images. But for now, let's build
it ourselves. This allows us to prove out the idea without yet requiring
changes in the rest of OpenShift.

The script added here looks wordy, but it's really trivial. It's
basically a glorified wrapper around podman build and skopeo copy so
that the built OCI image ends up in our meta.json.

Copy link

openshift-ci bot commented Mar 11, 2024

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

As part of openshift/os#799, we'll want to
build the "OCP node" image as a layered image on top of the RHCOS base
image.

Eventually, this image should be built outside our pipelines and more
like the rest of OpenShift container images. But for now, let's build
it ourselves. This allows us to prove out the idea without yet requiring
changes in the rest of OpenShift.

The script added here looks wordy, but it's really trivial. It's
basically a glorified wrapper around `podman build` and `skopeo copy` so
that the built OCI image ends up in our `meta.json`.
@jlebon
Copy link
Member Author

jlebon commented Apr 18, 2024

OK, actually I think I've convinced myself we don't need this intermediate stage. Instead, I think it's better to just go straight to having a follow-on job that builds the image and pushes it to the registry. This makes immediately palpable the distinct phases between the base compose using our usual cosa pipeline vs the layered build, which is how we want it set up in the long run.

@jlebon jlebon closed this Apr 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants