Source repo for Docker's Documentation
Go to file
Sarah Sanders 197da0c20e
admin: company freshness (#23061)
## Description
- Clean version of my company freshness, lint was picking up issues from
other branches?

## Reviews
- [ ] Editorial review
2025-07-10 10:01:52 -04:00
.github tooling: add prompts to vscode (#23030) 2025-07-08 17:27:47 +02:00
.vscode
_vale offload: add initial docs (#22910) 2025-07-10 12:09:07 +02:00
_vendor build: update buildx ref to 0.25.0 and buildkit ref to 0.23.2 2025-07-10 14:43:11 +02:00
archetypes
assets add MCP Gateway (#22935) 2025-07-09 16:56:49 +02:00
content admin: company freshness (#23061) 2025-07-10 10:01:52 -04:00
data offload: add initial docs (#22910) 2025-07-10 12:09:07 +02:00
hack
i18n
layouts admin: company freshness (#23061) 2025-07-10 10:01:52 -04:00
static ai tools: add MCP toolkit description (#22905) 2025-06-24 16:19:05 +02:00
.dockerignore
.gitattributes
.gitignore mcp OAuth and VS Code connection (#22904) 2025-07-03 15:04:26 +01:00
.htmltest.yml
.markdownlint.json
.prettierrc
.vale.ini
CONTRIBUTING.md
Dockerfile
LICENSE
Makefile
README.md
compose.yaml
docker-bake.hcl
go.mod build: update buildx ref to 0.25.0 and buildkit ref to 0.23.2 2025-07-10 14:43:11 +02:00
go.sum build: update buildx ref to 0.25.0 and buildkit ref to 0.23.2 2025-07-10 14:43:11 +02:00
hugo.yaml engine: docker 28.3.2 2025-07-09 17:51:19 +02:00
hugo_stats.json security: add k8s setting to reference (#23026) 2025-07-08 12:08:09 -04:00
netlify.toml
package-lock.json
package.json
pagefind.yml

README.md

Docs @ Docker

Welcome to Docker Documentation

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

Wed 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

    Request changes link

  • Click the Give feedback link on the side of every page in the docs.

    Docs feedback on each page

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 2013-2025 Docker, Inc., released under the Apache 2.0 license .