This adds a GitHub Actions workflow and supporting script to
automatically sync CLI documentation from the docker/cli repository on a
daily schedule.
<!--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
Signed-off-by: Paweł Gronowski <pawel.gronowski@docker.com>
## Description
In your Angular + Nginx Docker example you are running a non-root user,
but by default Nginx will try to write to directories like
`/var/cache/nginx/`. Which will cause errors like:
```
mkdir() "/var/cache/nginx/client_temp" failed (13: Permission denied)
```
This PR fixes that, and simply changing the default temp path
directories (like you did for the pid file as well) to the `/tmp`
directory. Which will work when using the `nginx` user in Docker. Mainly
`client_body_temp_path` change was needed here, but I would set more
just to be sure.
## Reviews
- [x] Technical review
- [x] Editorial review
- [ ] Product review
<!--Delete sections as needed -->
## Description
This PR moves the DCT retirement notice from a callout at the top of the
DOI section to a "Troubleshooting failed pulls" subsection at the end.
From a user's perspective:
- Many users don't have `DOCKER_CONTENT_TRUST=1` set and won't
experience any issues. A callout at the top of the page adds unnecessary
friction for users just trying to learn about DOI.
- Users trying to implement DCT will see notices in DCT docs
- Users experiencing pull failures will naturally look for
troubleshooting information. Placing this at the end of the section as a
dedicated troubleshooting subsection makes it easier to find when they
actually need it.
- The new structure follows a logical IA flow of learn about DOI →
understand how to use them → troubleshoot issues if they occur.
## 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>
This adds a GitHub Actions workflow and supporting script to
automatically sync CLI documentation from the docker/cli repository on a
daily schedule.
Signed-off-by: Paweł Gronowski <pawel.gronowski@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
## Description
Note: I can't run `hugo mod vendor`:
```
$ hugo mod vendor
WARN deprecated: the ":slugorfilename" permalink token was deprecated in Hugo 0.144.0 and will be removed in a future release. Use ":slugorcontentbasename" instead.
Error: html/template:redirect/single.html:1:13: no such template "_internal/alias.html"
```
## Related issues or tickets
## Reviews
- [ ] Technical review
- [ ] Editorial review
- [ ] Product review
---------
Signed-off-by: Nicolas De Loof <nicolas.deloof@gmail.com>
Co-authored-by: Allie Sadler <102604716+aevesdocker@users.noreply.github.com>
<!--Delete sections as needed -->
## Description
Update the Bun containerization Bun to reflect the new DHI access method
## Reviews
<!-- Notes for reviewers here -->
<!-- List applicable reviews (optionally @tag reviewers) -->
- [ ] Technical review
- [x] Editorial review
- [ ] Product review
<!--Delete sections as needed -->
## Description
Initially used a screenshot of a screenshot, which made it look grainy.
Updated.
Bonus: Normalized image sizes to at least the same height.
https://deploy-preview-23858--docsdocker.netlify.app/docker-hub/image-library/trusted-content/
## 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>
<!--Delete sections as needed -->
## Description
Clarify that you must log in using your Docker credentials (not some
special dhi credentials) with a link to create if necessary, noting that
it's free.
## Related issues or tickets
https://docker.slack.com/archives/C04BMTUC41E/p1765993571833459
## Reviews
<!-- Notes for reviewers here -->
<!-- List applicable reviews (optionally @tag reviewers) -->
- [ ] Editorial review
---------
Signed-off-by: Craig Osterhout <craig.osterhout@docker.com>
Co-authored-by: Allie Sadler <102604716+aevesdocker@users.noreply.github.com>
<!--Delete sections as needed -->
## Description
As discussed with Usha and Sarah (before she left) we agreed we'd have
the subscription page link to the official pricing page to have a single
source of truth. Simplifies maintenance and the pricing page already
does a good job of communicating everything.
## 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
Issue: The navigation changes based on entitlement.
Fix:
- Updated step to list both possible navs.
- Removed screenshots. They were included originally to show where the
nav was because the nav magically appeared when gaining entitlement.
## 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>
<!--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
