7543797115
## Description This PR updates the Docker Build Cloud CI documentation to clarify the setup of credentials for CI/CD pipelines. The changes include: - Renaming the section to “Setting up credentials for CI/CD” and integrating guidance on both access tokens and the required username (`DOCKER_USER`). - Explaining when to use an organization access token (OAT) versus a personal access token (PAT), and which value to use for `DOCKER_USER` in each case. - Updating the build timeout note from 2 hours to 90 minutes. ## Related issues or tickets N/A – Documentation improvement and clarification. ## Reviews - [ ] Technical review — Confirm technical accuracy of credential setup and variable usage. - [ ] Editorial review — Check for clarity, consistency, and adherence to Docker copy guidelines. - [ ] Product review — Ensure the documentation aligns with product requirements and user needs. |
||
|---|---|---|
| .github | ||
| _vale | ||
| _vendor | ||
| archetypes | ||
| assets | ||
| content | ||
| data | ||
| hack | ||
| i18n | ||
| layouts | ||
| static | ||
| .dockerignore | ||
| .gitattributes | ||
| .gitignore | ||
| .htmltest.yml | ||
| .markdownlint.json | ||
| .prettierrc | ||
| .vale.ini | ||
| CONTRIBUTING.md | ||
| Dockerfile | ||
| LICENSE | ||
| Makefile | ||
| README.md | ||
| compose.yaml | ||
| docker-bake.hcl | ||
| go.mod | ||
| go.sum | ||
| hugo.yaml | ||
| hugo_stats.json | ||
| netlify.toml | ||
| package-lock.json | ||
| package.json | ||
| pagefind.yml | ||
| postcss.config.js | ||
| tailwind.config.js | ||
README.md
Docs @ Docker
Welcome to the Docker Documentation repository. This is the source for https://docs.docker.com/.
Feel free to send us pull requests and file issues. Our docs are completely open source, and we deeply appreciate contributions from the Docker community!
Provide feedback
We’d love to hear your feedback. Please file documentation issues only in the Docs GitHub repository. You can file a new issue to suggest improvements or if you see any errors in the existing documentation.
Before submitting a new issue, check whether the issue has already been reported. You can join the discussion using an emoji, or by adding a comment to an existing issue. If possible, we recommend that you suggest a fix to the issue by creating a pull request.
You can ask general questions and get community support through the Docker Community Slack. Personalized support is available through the Docker Pro, Team, and Business subscriptions. See Docker Pricing for details.
If you have an idea for a new feature or behavior change in a specific aspect of Docker or have found a product bug, file that issue in the project's code repository.
We've made it easy for you to file new issues.
-
Click New issue on the docs repository and fill in the details, or
-
Click Request docs changes in the right column of every page on docs.docker.com and add the details, or
-
Click the Give feedback link on the side of every page in the docs.
Contribute to Docker docs
We value your contribution. We want to make it as easy as possible to submit
your contributions to the Docker docs repository. Changes to the docs are
handled through pull requests against the main branch. To learn how to
contribute, see CONTRIBUTING.md.
Copyright and license
Copyright 2013-2025 Docker, Inc., released under the Apache 2.0 license .