[docs-scanner] S3 and Azure Blob cache backends marked as unreleased but have complete documentation
Maintainers usually reply within 1 day
@dave123981 is already working on this.
Since Nov 10, 2026.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 66/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- markdown
- Domain
- documentation
Research direction
Start with content/manuals/build/cache/backends/_index.md, then compare its S3 and Azure Blob status labels with s3.md and azblob.md in the same directory. Check the feature status against the documentation evidence, then make the overview and individual pages consistent; done when readers can tell whether both backends are available or experimental.
Written by the indexing model from the issue text.
Description
File: content/manuals/build/cache/backends/_index.md
Issue
The main cache backends overview page marks S3 and Azure Blob Storage as "(unreleased)":
s3: uploads the build cache to an
AWS S3 bucket (unreleased).
azblob: uploads the build cache to
Azure Blob Storage
(unreleased).
However, both s3.md and azblob.md in the same directory contain complete, production-ready documentation with:
- Full synopsis and usage examples
- Complete parameter tables
- Authentication instructions
- Summary bars indicating feature status (not unreleased status)
Why this matters
Readers see "(unreleased)" on the overview page and may assume these features aren't available yet, when in fact they have complete documentation suggesting they are released features. This creates confusion about whether users can actually use these cache backends.
Suggested fix
Either:
- Remove the "(unreleased)" designation if these features are actually released and available
- Or, if they truly are unreleased/experimental, add clear experimental/beta warnings to the individual documentation pages and explain what "unreleased" means (e.g., "available in BuildKit but not yet in stable Docker release")
The individual pages should match the status indicated in the overview.
Found by nightly documentation quality scanner
- Dominant language
- Markdown
- Stars
- 4.7k
- Forks
- 8.5k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 139
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from docker/docs
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
[docs-scanner] Inline cache missing driver/containerd requirement that overview page statesPossibly taken @himanchalkaushale claimed this 1 day ago. Open
Difficulty 1/5 Under an hour Newbie friendliness 95/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
status/triage
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Maintainers usually reply within 1 day
-
[docs-scanner] Confusing explanation of approval-required outcome vs permit in MCP policyPossibly taken @dave123981 claimed this 4 days ago. Open
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
line/centraldogma#1397 ·
Maintainers usually reply within 2 days
-
🐞 bug 🧐 unconfirmed
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Tencent/tdesign-vue-next#7056 · 1 comment ·
Maintainers usually reply within 1 day
-
area: docs documentation good first issue priority: low size: XS status: needs triage
Difficulty 1/5 1-3 hours Newbie friendliness 92/100
cubrid-lab/sqlalchemy-cubrid#1294 ·
Maintainers usually reply within 1 day
-
a: plugins d: docs/ fyi-macos P2 platform-ios platform-macos team-ios
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
kubescape/cel-admission-library#141 · 1 comment ·
Maintainers usually reply within 1 day