Skip to content

Conversation

@mburke5678
Copy link
Contributor

@mburke5678 mburke5678 commented Jul 28, 2025

Per Mark Russell: Docs should have bootc container lint everywhere it says ostree container commit in 4.19+
https://issues.redhat.com/browse/OCPBUGS-59846

Link to docs preview:
Example Containerfiles -- Updated examples throughout
Using the on-cluster image mode to apply a custom layered image -- Updated example in Step 1.

QE review:

  • QE has approved this change.

@mburke5678 mburke5678 added this to the Continuous Release milestone Jul 28, 2025
@openshift-ci openshift-ci bot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Jul 28, 2025
@ocpdocs-previewbot
Copy link

🤖 Mon Jul 28 14:52:37 - Prow CI generated the docs preview:

https://96758--ocpdocs-pr.netlify.app/openshift-enterprise/latest/machine_configuration/mco-coreos-layering.html

@openshift-ci
Copy link

openshift-ci bot commented Jul 28, 2025

@mburke5678: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@mburke5678 mburke5678 changed the title OCPBUGS 59846 OCP image mode docs should use OCPBUGS 59846 OCP image mode docs should use "bootc container lint" Jul 28, 2025
@mburke5678
Copy link
Contributor Author

@cheesesashimi Can you PTAL at this PR?

@bergerhoffer
Copy link
Contributor

The branch/enterprise-4.21 label has been added to this PR.

This is because your PR targets the main branch and is labeled for enterprise-4.20. And any PR going into main must also target the latest version branch (enterprise-4.21).

If the update in your PR does NOT apply to version 4.21 onward, please re-target this PR to go directly into the appropriate version branch or branches (enterprise-4.x) instead of main.

@openshift-bot
Copy link

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

branch/enterprise-4.19 branch/enterprise-4.20 branch/enterprise-4.21 lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants