ROCm Container Documentation Standards RFC - #6972
Draft
LiamfBerry wants to merge 2 commits into
Draft
Conversation
✅ All Checks Passed — Ready for Review
📖 Need help? See the Policy FAQ for details on every check and how to fix failures. |
|
🎉 All checks passed! This PR is ready for review. |
Pre-commit check failed⛔ pre-commit failed Please run locally:
This repo uses |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation
ROCm's container catalog spans 93 Docker Hub repos, and the Docker Hub overview is the first — often the only — documentation a user sees before pulling an image. Today those overviews are inconsistent or absent: the most-pulled Core SDK/Runtime image, rocm/dev-ubuntu-24.04 (100K+ pulls), shows "No overview available" — no prerequisites, no run command beyond a bare docker pull, no support contact, no security information. There is no shared definition of what a ROCm container's documentation must contain, so each repo documents (or doesn't) on its own terms.
Technical Details
This RFC defines the documentation standard every ROCm Core SDK/Runtime container must meet. It is a companion to the naming, tagging, layering, and lifecycle rules in RFC0013 — ROCm Core SDK & Runtime Container Standardization; RFC0013 references this document as the authoritative source for the documentation requirement.
JIRA ID
ROCM-28753
Test Plan
N/A
Test Result
N/A
Submission Checklist