Docker Desktop sandboxes and docker sandbox CLI reference pages needed to be marked deprecated while removing sbx experimental callouts.
Updated sandbox docs, retired products listing, and sandbox CLI metadata so the deprecated state is reflected consistently.
Generated by Codex
Signed-off-by: David Karlsson <35727626+dvdksn@users.noreply.github.com>
<!--Delete sections as needed -->
## Description
- Adds VEX status reference and `not_affected` justification codes based
on OpenVEX and usage in the advisory repo.
- Adds "Why DHI does not use `fixed`"
- Removes "Why is VEX important?" and "How DHI integrates VEX" sections.
This content is covered more concretely in `scanner-integrations.md`.
Will follow up to figure out how to cover the content better between
these two topics, but removing redundant content for now.
https://deploy-preview-24838--docsdocker.netlify.app/dhi/core-concepts/vex/
## Related issues or tickets
ENGDOCS-3238
## Reviews
<!-- Notes for reviewers here -->
<!-- List applicable reviews (optionally @tag reviewers) -->
- [ ] Technical review
- [ ] Editorial review
---------
Signed-off-by: Craig Osterhout <craig.osterhout@docker.com>
<!--Delete sections as needed -->
## Description
<!-- Tell us what you did and why -->
## Related issues or tickets
<!-- Related issues, pull requests, or Jira tickets -->
## Reviews
<!-- Notes for reviewers here -->
<!-- List applicable reviews (optionally @tag reviewers) -->
- [ ] Technical review
- [ ] Editorial review
- [ ] Product review
<!--Delete sections as needed -->
## Description
Tested and updated the dotnet guide.
- Add missing stage name for dhi Dockerfile
- Clean up some output
## Related issues or tickets
<!-- Related issues, pull requests, or Jira tickets -->
## Reviews
<!-- Notes for reviewers here -->
<!-- List applicable reviews (optionally @tag reviewers) -->
- [ ] Editorial review
Signed-off-by: Craig Osterhout <craig.osterhout@docker.com>
The Kubernetes driver page did not describe the new persistent-volume-claim.requests.storage option added in Buildx.\n\nDocument the option, explain that it switches the workload to a StatefulSet, and show that it persists the build cache per replica.
The platform table on `engine/install/_index.md` listed `SLES` with an ❌
in the s390x column, which reads as if SLES is unsupported in general.
The linked `sles.md` is actually scoped to SLES on s390x (the page's own
`linkTitle` is already `SLES (s390x)`).
Align the table label with the page's `linkTitle` so the
architecture-specific scope is visible without clicking through.
Fixes#24862
The 'Service users for team autobuilds' section lives in setup.md,
not in _index.md. Point the 'create a service account' link to
setup.md#service-users-for-team-autobuilds so it resolves correctly.
Two links pointed to index.md#regexes-and-automated-builds, but the
'Regexes and automated builds' section lives in setup.md itself.
Use same-file anchors so the links resolve correctly.
PR to capture work:
- Update / simplify titles to match docs
- Create subcategories within org/company
- Wrestle with redirect nightmare part 2
Filing a follow up PR to create parallel structure in the `Company`
subcategory. This PR's scope is for `Organization` only.
## Summary
Standardize the Docker Scout CLI command on `docker scout` (with space)
across the CircleCI and Jenkins integration guides so it matches the
format used in `azure.md`, `gitlab.md`, and the rest of the Scout docs
(`install.md`, `quickstart.md`, `gha.md`).
## Issue
Fixes#24843
## Changes
- `content/manuals/scout/integrations/ci/circle-ci.md`: change
`docker-scout cves …` to `docker scout cves …`
- `content/manuals/scout/integrations/ci/jenkins.md`: change
`docker-scout cves …` to `docker scout cves …`
Other references to `docker-scout` that are not CLI invocations (the
binary filename in `install.md`, the GitHub Action step `id:
docker-scout` in `gha.md`, external URLs, and Azure resource names) are
intentionally left unchanged.
## Testing
- Docs-only change. Diff is two lines, no content rewrites.
Signed-off-by: Niels Kaspers <kaspersniels@gmail.com>
<!--Delete sections as needed -->
## Description
<!-- Tell us what you did and why -->
## Related issues or tickets
<!-- Related issues, pull requests, or Jira tickets -->
## Reviews
<!-- Notes for reviewers here -->
<!-- List applicable reviews (optionally @tag reviewers) -->
- [ ] Technical review
- [ ] Editorial review
- [ ] Product review
The code snippet for Dockerfile under the "Using the official Docker
images" contains a comment which says that this Docker file uses DHI
image, which is incorrect.
<!--Delete sections as needed -->
Updated the code snippet to match the tab contents
<!-- Tell us what you did and why -->
## Reviews
<!-- Notes for reviewers here -->
<!-- List applicable reviews (optionally @tag reviewers) -->
- [ ] Technical review
- [ ] Editorial review
- [ ] Product review
Fixes#24818.
The `[!IMPORTANT]` callout at the top of
`content/manuals/dhi/how-to/build.md` read:
> You must authenticate to the Docker Hardened Images registry
(`dhi.io`) to pull base images and build tools. [...]
Phrased that way it reads as if any Dockerfile using a DHI base image
(e.g. `FROM dhi.io/python:3.13`) needs a special authentication step
specific to the build page. The real reason is scoped: the DHI build
frontend itself pulls from `dhi.io` when processing a YAML definition
file.
Rewritten to tie the requirement explicitly to the DHI build system and
to the act of building a definition file, so readers don't extrapolate
the requirement to unrelated Dockerfile usage. Wording around the Docker
ID credentials is preserved.
Fixes#24819.
In `content/manuals/dhi/how-to/customize.md` the Docker Hub tab jumped
from "select the repository / select the tag" straight to "images later
in the list will overwrite files from earlier images" without first
establishing that multiple OCI artifacts can be added or how their
ordering is determined in the UI. Readers understood the consequence but
not the mechanism.
Adds one short paragraph before the overwrite rule to anchor the reader:
- multiple OCI artifacts can be added to a single customization,
- they're applied in the order they're added in the **OCI artifacts**
drop-down.
The overwrite rule is rephrased to:
- refer to "images added later / images added earlier" for consistency
with the new paragraph,
- use "If multiple images contain directories or files with the same
path" (the rule applies to any N≥2, not just two),
- use "directories or files" instead of the existing "directories and
files", which could be read as requiring both types in the same artifact
for the rule to apply.
No change to the subsequent paragraphs about include/exclude paths.
Fixes#24743.
The authentication note at the top of
`content/manuals/dhi/migration/examples/python.md` was the stripped-down
version, missing:
- the indication that `docker login dhi.io` expects Docker ID
credentials
- the detail that those are the same credentials as Docker Hub
- the link to the account creation page
The equivalent notes in `go.md` (lines 24-29) and `node.md` (lines
24-29) carry all three. This PR copies the full paragraph into
`python.md` so Python readers get the same onboarding guidance.
No other content changed.
Fast follow ups:
- Returned aliases with new alias to one doc
- Updated provision index page to accurately reflect different methods
- reorganized table to reflect popularity of methods based off sme info
(scim is the vogue, then JIT, then auto provision)
- Updated grid to link correctly to auto provisioning doc
- Created more opinionated left nav to reflect recommendations around
security SCIM > JIT > auto
- Fixed `*`s to be `-`s
- Updated Migrate doc heading levels
<!--Delete sections as needed -->
## Description
<!-- Tell us what you did and why -->
## Related issues or tickets
<!-- Related issues, pull requests, or Jira tickets -->
## Reviews
<!-- Notes for reviewers here -->
<!-- List applicable reviews (optionally @tag reviewers) -->
- [ ] Technical review
- [ ] Editorial review
- [ ] Product review
---------
Co-authored-by: David Karlsson <35727626+dvdksn@users.noreply.github.com>
Adds a troubleshooting note on the Fedora install page for the case
where the Docker service fails to start with `failed to find iptables`
in the logs, pointing users to set the `iptables` alternative to
`iptables-nft`.
Closes#23186
<!--Delete sections as needed -->
## Description
Adds documentation for `network_mode: bridge` in the Compose file
reference.
While `bridge` is a valid and functional network_mode option that
connects
containers to the host's default bridge network, it was not documented
alongside the other options (none, host, service, container).
Fixes#24742.
- #24742
<!-- Related issues, pull requests, or Jira tickets -->
## Reviews
<!-- Notes for reviewers here -->
<!-- List applicable reviews (optionally @tag reviewers) -->
- [x] Technical review
- [ ] Editorial review
- [ ] Product review
---------
Signed-off-by: Mahitha Adapa <mahitha.ada@gmail.com>
Co-authored-by: Allie Sadler <102604716+aevesdocker@users.noreply.github.com>
