4f6a42110e
Before this, docker compose would always first pull the `docs/docstage` image from docker hub, then build the local docs: Before this: ``` docker compose up [+] Running 1/12 ⠿ docs Pulled 11.1s ⠧ 706c320525cd Download complete 8.7s ⠴ 4f98bba63633 Download complete 7.5s ⠇ 4f4fb700ef54 Exists 4.8s ⠇ a47abff02990 Download complete 4.8s ⠧ ab1af07f990a Download complete 4.7s ⠧ bd5777bb8f79 Download complete 4.7s ⠧ 8b79b42c3524 Download complete 4.7s ⠧ d4b8ebd00804 Download complete 4.7s ⠧ f1398ae18173 Download complete 4.7s ⠧ 9981e73032c8 Download complete 4.7s ⠧ e5f90f35b4bc Download complete 4.7s [+] Building 69.1s (15/20) => [internal] load .dockerignore 0.0s => => transferring context: 196B 0.0s => [internal] load build definition from Dockerfile 0.0s => => transferring dockerfile: 3.85kB 0.0s => resolve image config for docker.io/docker/dockerfile:1 2.2s ... ``` With this patch, the `docs pulled` step is skipped, and we start building immediately: ``` docker compose up [+] Building 6.7s (11/20) => [internal] load .dockerignore 0.0s => => transferring context: 196B 0.0s => [internal] load build definition from Dockerfile 0.0s ... ``` Perhaps compose does this as it was to help with caching when building with the legacy builder, but BuildKit does not use local images for caching, so we don't need to do so (I'm planning to open a ticket in compose to discuss this). As we're using this compose-file to build the docs (not to view some older version), let's disable pulling, so that we're always building. Signed-off-by: Sebastiaan van Stijn <github@gone.nl> |
||
|---|---|---|
| .docker | ||
| .github | ||
| _data | ||
| _deploy/nginx | ||
| _includes | ||
| _layouts | ||
| _plugins | ||
| _releaser | ||
| _scss | ||
| assets | ||
| atomist | ||
| build | ||
| cloud | ||
| compose | ||
| config | ||
| contribute | ||
| desktop | ||
| develop | ||
| docker-hub | ||
| docker-id | ||
| engine | ||
| get-started | ||
| language | ||
| network | ||
| reference | ||
| registry | ||
| release-notes | ||
| samples | ||
| security | ||
| single-sign-on | ||
| storage | ||
| subscription | ||
| support | ||
| .dockerignore | ||
| .editorconfig | ||
| .env | ||
| .gitattributes | ||
| .gitignore | ||
| .markdownlint.json | ||
| .markdownlint.rb | ||
| .nojekyll | ||
| .ruby-version | ||
| .vale.ini | ||
| 404.md | ||
| CONTRIBUTING.md | ||
| Dockerfile | ||
| Gemfile | ||
| Gemfile.lock | ||
| LICENSE | ||
| Makefile | ||
| README.md | ||
| _config.yml | ||
| _config_production.yml | ||
| _config_stage.yml | ||
| _redirects.yml | ||
| docker-bake.hcl | ||
| docker-compose.yml | ||
| docsarchive.md | ||
| get-docker.md | ||
| glossary.md | ||
| google161104f9fdea6089.html | ||
| googlecbe7fee896be512c.html | ||
| index.md | ||
| release-lifecycle.md | ||
| robots.txt | ||
| search.md | ||
| sitemap.xsl | ||
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 really 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.
Contribute to Docker docs
We value your contribution. We'd like 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 master branch. To learn how to
contribute, see our Contribute section.
Copyright and license
Copyright 2013-2022 Docker, inc, released under the Apache 2.0 license.