mirror of https://github.com/docker/docs.git
Spelling fixes (#21230)
Christmas is early :) and i had some free time to go over all the documents and fix all spelling mistakes i have found.
This commit is contained in:
Arie Heinrich
GitHub
parent
ce7d86cc25
commit
c17faccf17
|
|
@ -18,7 +18,7 @@ You can also make a badge a link.
|
|||
|
||||
### Usage guidelines
|
||||
|
||||
We use badges to indicate new content and product content in various stages of the release lifcycle:
|
||||
We use badges to indicate new content and product content in various stages of the release lifecycle:
|
||||
|
||||
- The violet badge to highlight new early access or experimental content
|
||||
- The blue badge to highlight beta content
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
title: "Demo: set up and use Docker Build Cloud in development"
|
||||
description: Learn how to use Docker Buld Cloud for local builds.
|
||||
description: Learn how to use Docker Build Cloud for local builds.
|
||||
weight: 20
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@
|
|||
title: Containerize a generative AI application
|
||||
linkTitle: Containerize your app
|
||||
weight: 10
|
||||
keywords: python, generative ai, genai, llm, neo4j, ollama, containerize, intitialize, langchain, openai
|
||||
keywords: python, generative ai, genai, llm, neo4j, ollama, containerize, initialize, langchain, openai
|
||||
description: Learn how to containerize a generative AI (GenAI) application.
|
||||
aliases:
|
||||
- /guides/use-case/genai-pdf-bot/containerize/
|
||||
|
|
|
|||
|
|
@ -106,7 +106,7 @@ When running Ollama in a container, you should have a CUDA-supported GPU. While
|
|||
To run Ollama in a container and provide GPU access:
|
||||
|
||||
1. Install the prerequisites.
|
||||
- For Docker Engine on Linux, install the [NVIDIA Container Toolkilt](https://github.com/NVIDIA/nvidia-container-toolkit).
|
||||
- For Docker Engine on Linux, install the [NVIDIA Container Toolkit](https://github.com/NVIDIA/nvidia-container-toolkit).
|
||||
- For Docker Desktop on Windows 10/11, install the latest [NVIDIA driver](https://www.nvidia.com/Download/index.aspx) and make sure you are using the [WSL2 backend](/manuals/desktop/wsl/_index.md#turn-on-docker-desktop-wsl-2)
|
||||
2. Add the Ollama service and a volume in your `compose.yaml`. The following is
|
||||
the updated `compose.yaml`:
|
||||
|
|
|
|||
|
|
@ -153,7 +153,7 @@ RUN java -Djarmode=layertools -jar target/app.jar extract --destination target/e
|
|||
# The example below uses eclipse-turmin's JRE image as the foundation for running the app.
|
||||
# By specifying the "17-jre-jammy" tag, it will also use whatever happens to be the
|
||||
# most recent version of that tag when you build your Dockerfile.
|
||||
# If reproducability is important, consider using a specific digest SHA, like
|
||||
# If reproducibility is important, consider using a specific digest SHA, like
|
||||
# eclipse-temurin@sha256:99cede493dfd88720b610eb8077c8688d3cca50003d76d1d539b0efc8cca72b4.
|
||||
FROM eclipse-temurin:17-jre-jammy AS final
|
||||
|
||||
|
|
|
|||
|
|
@ -126,7 +126,7 @@ managed by Docker.
|
|||
When you remove a container, all data in that container is deleted. To save
|
||||
notebooks outside of the container, you can use a [volume](/engine/storage/volumes/).
|
||||
|
||||
### Run a JupterLab container with a volume
|
||||
### Run a JupyterLab container with a volume
|
||||
|
||||
To start the container with a volume, open a terminal and run the following command
|
||||
|
||||
|
|
@ -378,7 +378,7 @@ To share your image and data, you'll use [Docker Hub](https://hub.docker.com/).
|
|||
Other users can now download and run your image using the `docker run` command. They need to replace `YOUR-USER-NAME` with your Docker ID.
|
||||
|
||||
```console
|
||||
$ docker run --rm -p 8889:8888 YOUR-USER-NAME/my-jupyer-image start-notebook.py --NotebookApp.token='my-token'
|
||||
$ docker run --rm -p 8889:8888 YOUR-USER-NAME/my-jupyter-image start-notebook.py --NotebookApp.token='my-token'
|
||||
```
|
||||
|
||||
### Share your volume
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@
|
|||
title: Containerize a RAG application
|
||||
linkTitle: Containerize your app
|
||||
weight: 10
|
||||
keywords: python, generative ai, genai, llm, ollama, containerize, intitialize, qdrant
|
||||
keywords: python, generative ai, genai, llm, ollama, containerize, initialize, qdrant
|
||||
description: Learn how to containerize a RAG application.
|
||||
aliases:
|
||||
- /guides/use-case/rag-ollama/containerize/
|
||||
|
|
|
|||
|
|
@ -147,7 +147,7 @@ For the sample application, you'll use a variation of the backend from the react
|
|||
# The example below uses the debian bullseye image as the foundation for running the app.
|
||||
# By specifying the "bullseye-slim" tag, it will also use whatever happens to be the
|
||||
# most recent version of that tag when you build your Dockerfile. If
|
||||
# reproducability is important, consider using a digest
|
||||
# reproducibility is important, consider using a digest
|
||||
# (e.g., debian@sha256:ac707220fbd7b67fc19b112cee8170b41a9e97f703f588b2cdbbcdcecdd8af57).
|
||||
FROM debian:bullseye-slim AS final
|
||||
|
||||
|
|
|
|||
|
|
@ -13,7 +13,7 @@ Bake is an experimental feature, and we are looking for
|
|||
|
||||
{{% /experimental %}}
|
||||
|
||||
Bake is a feature of Docker Buildx that lets you define your build configuraton
|
||||
Bake is a feature of Docker Buildx that lets you define your build configuration
|
||||
using a declarative file, as opposed to specifying a complex CLI expression. It
|
||||
also lets you run multiple builds concurrently with a single invocation.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
title: Build cache invalidation
|
||||
description: Dig into the details abouw how cache invalidation works for Docker's build cache
|
||||
description: Dig into the details about how cache invalidation works for Docker's build cache
|
||||
keywords: build, buildx, buildkit, cache, invalidation, cache miss
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
title: GitHub Actions build summary
|
||||
linkTitle: Build summary
|
||||
descripion: Get an overview of your Docker Builds with GitHub Actions
|
||||
description: Get an overview of your Docker Builds with GitHub Actions
|
||||
keywords: github actions, gha, build, summary, annotation
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@
|
|||
title: Using profiles with Compose
|
||||
linkTitle: Use service profiles
|
||||
weight: 20
|
||||
desription: How to use profiles with Docker Compose
|
||||
description: How to use profiles with Docker Compose
|
||||
keywords: cli, compose, profile, profiles reference
|
||||
aliases:
|
||||
- /compose/profiles/
|
||||
|
|
|
|||
|
|
@ -794,7 +794,7 @@ This release fixes a build issue with Docker Desktop for Windows introduced in C
|
|||
|
||||
* Added support of the `privileged` attribute in the `service.build` section. Pull Request [compose#10112](https://github.com/docker/compose/pull/10112)
|
||||
* Introduced `--ignore-buildable` to ignore buildable images on pull. Fixed [compose#8805](https://github.com/docker/compose/issues/8805)
|
||||
* Introduceed `--no-attach` to ignore some service outputs. Fixed [compose#8546](https://github.com/docker/compose/issues/8546)
|
||||
* Introduced `--no-attach` to ignore some service outputs. Fixed [compose#8546](https://github.com/docker/compose/issues/8546)
|
||||
* Fixed issue with `logs` when `driver:none` is set. Fixed [compose#9030](https://github.com/docker/compose/issues/9030)
|
||||
* Compose now relies on dockerCLI.streams. Pull Request [compose#10082](https://github.com/docker/compose/pull/10082)
|
||||
* Fixed issue with service hash that MUST exclude replicas. Fixed [compose#10077](https://github.com/docker/compose/issues/10077)
|
||||
|
|
@ -955,7 +955,7 @@ For the full change log or additional information, check the [Compose repository
|
|||
- Fixed intermittent conflict errors when using `depends_on`. Fixes [compose#9014](https://github.com/docker/compose/issues/9014)
|
||||
- Cleared service `CMD` when entry point is overridden. Fixes [compose#9622](https://github.com/docker/compose/issues/9622)
|
||||
- Configured default builder export when no `build.platforms` defined. Fixes [compose#9856](https://github.com/docker/compose/issues/9856)
|
||||
- Fixed a bug to keep the platform defined, in priority, via DOCKER_DEFAULT_PLATFORM or the `service.platform` attribut. Fixes [compose#9864](https://github.com/docker/compose/issues/9864)
|
||||
- Fixed a bug to keep the platform defined, in priority, via DOCKER_DEFAULT_PLATFORM or the `service.platform` attribute. Fixes [compose#9864](https://github.com/docker/compose/issues/9864)
|
||||
- Removed support for `DOCKER_HOST` in `.env` files. Fixes [compose#9210](https://github.com/docker/compose/issues/9210)
|
||||
- Fixed a bug to ensure clean service command if entry point is overridden in run command. Fixes [compose#9622](https://github.com/docker/compose/issues/9622)
|
||||
- Deps: fixed race condition during graph traversal. Fixes [compose#9014](https://github.com/docker/compose/issues/9014)
|
||||
|
|
@ -1270,7 +1270,7 @@ For the full change log or additional information, check the [Compose repository
|
|||
- Provided checksums.txt file and added `--binary` to allow verification in different OS. Fixes [#9388](https://github.com/docker/compose/issues/9388).
|
||||
- Added changes so locally pulled image's ID is inspected and persisted to `com.docker.compose.image`. Fixes [#9357](https://github.com/docker/compose/issues/9357).
|
||||
- Fixed issue regarding IPAM gateway setup. Fixes [#9330](https://github.com/docker/compose/issues/9330).
|
||||
- Added support for ppc64le archictecture for docker compose binary.
|
||||
- Added support for ppc64le architecture for docker compose binary.
|
||||
- Fixed search/replace typo in `--no-TTY` documentation.
|
||||
|
||||
For the full change log or additional information, check the [Compose repository 2.5.0 release page](https://github.com/docker/compose/releases/tag/v2.5.0).
|
||||
|
|
|
|||
|
|
@ -97,7 +97,7 @@ Take a look at the [Docker Public Roadmap](https://github.com/orgs/docker/projec
|
|||
|
||||
#### For all platforms
|
||||
|
||||
- Fixed a bug that caused the CLI to become idle when a container was started with AutoRemove (`--rm`) but whose port bindings would be rejected by Docker Dekstop at start-up.
|
||||
- Fixed a bug that caused the CLI to become idle when a container was started with AutoRemove (`--rm`) but whose port bindings would be rejected by Docker Desktop at start-up.
|
||||
- Fixed a bug where diagnostics collection would fail sporadically on the **Support** screen.
|
||||
- Fixed a bug where folders wouldn't expand in a container's **File** tab. Fixes [docker/for-win#14204](https://github.com/docker/for-win/issues/14204).
|
||||
- In-app updates now respect the proxy settings.
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
description: How to uninstall Docker Desktop
|
||||
keywords: Windows, unintall, Mac, Linux, Docker Desktop
|
||||
keywords: Windows, uninstall, Mac, Linux, Docker Desktop
|
||||
title: Uninstall Docker Desktop
|
||||
linkTitle: Uninstall
|
||||
weight: 210
|
||||
|
|
|
|||
|
|
@ -88,7 +88,7 @@ and select the **System default** option under **Choose your terminal**.
|
|||
|
||||
#### Open the integrated terminal in debug mode
|
||||
|
||||
Debug mode requires a [Pro, Team, or Business subcription](/subscription/details/). Debug mode has several advantages, such as:
|
||||
Debug mode requires a [Pro, Team, or Business subscription](/subscription/details/). Debug mode has several advantages, such as:
|
||||
|
||||
- A customizable toolbox. The toolbox comes with many standard Linux tools
|
||||
pre-installed, such as `vim`, `nano`, `htop`, and `curl`. For more details, see the [`docker debug` CLI reference](/reference/cli/docker/debug/).
|
||||
|
|
|
|||
|
|
@ -236,7 +236,7 @@ Each organization page now breaks down into these tabs:
|
|||
* **New:** Teams - search by team or username, and open up any team page to
|
||||
manage the team
|
||||
* **New:** Invitees (conditional tab, only if an invite exists) - resend or
|
||||
remove invitiations from this tab
|
||||
remove invitations from this tab
|
||||
* Repositories
|
||||
* Settings
|
||||
* Billing
|
||||
|
|
|
|||
|
|
@ -78,7 +78,7 @@ toc_max: 2
|
|||
* Add `--format` option to `docker node ls` [#30424](https://github.com/docker/docker/pull/30424)
|
||||
* Add `--prune` option to `docker stack deploy` to remove services that are no longer defined in the docker-compose file [#31302](https://github.com/docker/docker/pull/31302)
|
||||
* Add `PORTS` column for `docker service ls` when using `ingress` mode [#30813](https://github.com/docker/docker/pull/30813)
|
||||
- Fix unnescessary re-deploying of tasks when environment-variables are used [#32364](https://github.com/docker/docker/pull/32364)
|
||||
- Fix unnecessary re-deploying of tasks when environment-variables are used [#32364](https://github.com/docker/docker/pull/32364)
|
||||
- Fix `docker stack deploy` not supporting `endpoint_mode` when deploying from a docker compose file [#32333](https://github.com/docker/docker/pull/32333)
|
||||
- Proceed with startup if cluster component cannot be created to allow recovering from a broken swarm setup [#31631](https://github.com/docker/docker/pull/31631)
|
||||
|
||||
|
|
|
|||
|
|
@ -39,7 +39,7 @@ toc_max: 2
|
|||
|
||||
* Gracefully remove LB endpoints from services [docker/libnetwork#2112](https://github.com/docker/libnetwork/pull/2112)
|
||||
* Retry other external DNS servers on ServFail [docker/libnetwork#2121](https://github.com/docker/libnetwork/pull/2121)
|
||||
* Improve scalabiltiy of bridge network isolation rules [docker/libnetwork#2117](https://github.com/docker/libnetwork/pull/2117)
|
||||
* Improve scalability of bridge network isolation rules [docker/libnetwork#2117](https://github.com/docker/libnetwork/pull/2117)
|
||||
* Allow for larger preset property values, do not override [docker/libnetwork#2124](https://github.com/docker/libnetwork/pull/2124)
|
||||
* Prevent panics on concurrent reads/writes when calling `changeNodeState` [docker/libnetwork#2136](https://github.com/docker/libnetwork/pull/2136)
|
||||
|
||||
|
|
|
|||
|
|
@ -31,7 +31,7 @@ toc_max: 2
|
|||
- Allow for larger preset property values, do not override. [docker/libnetwork#2124](https://github.com/docker/libnetwork/pull/2124)
|
||||
- networkdb: User write lock in handleNodeEvent. [docker/libnetwork#2136](https://github.com/docker/libnetwork/pull/2136)
|
||||
* Import libnetwork fix for rolling updates. [moby/moby#36638](https://github.com/moby/moby/pull/36638)
|
||||
* Update libnetwork to improve scalabiltiy of bridge network isolation rules. [moby/moby#36774](https://github.com/moby/moby/pull/36774)
|
||||
* Update libnetwork to improve scalability of bridge network isolation rules. [moby/moby#36774](https://github.com/moby/moby/pull/36774)
|
||||
- Fix a misused network object name. [moby/moby#36745](https://github.com/moby/moby/pull/36745)
|
||||
|
||||
### Runtime
|
||||
|
|
|
|||
|
|
@ -8,13 +8,13 @@ The easiest way to deploy Notary Server is by using Docker Compose. To follow th
|
|||
|
||||
1. Clone the Notary repository.
|
||||
|
||||
```consolse
|
||||
```console
|
||||
$ git clone https://github.com/theupdateframework/notary.git
|
||||
```
|
||||
|
||||
2. Build and start Notary Server with the sample certificates.
|
||||
|
||||
```consolse
|
||||
```console
|
||||
$ docker compose up -d
|
||||
```
|
||||
|
||||
|
|
|
|||
|
|
@ -222,7 +222,7 @@ import {
|
|||
} from "@mui/material";
|
||||
import { createDockerDesktopClient } from "@docker/extension-api-client";
|
||||
|
||||
//obtain docker destkop extension client
|
||||
//obtain docker desktop extension client
|
||||
const ddClient = createDockerDesktopClient();
|
||||
|
||||
export function App() {
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
title: Package and release your extension
|
||||
description: Docker extension disctribution
|
||||
description: Docker extension distribution
|
||||
keywords: Docker, extensions, sdk, distribution
|
||||
aliases:
|
||||
- /desktop/extensions-sdk/extensions/DISTRIBUTION/
|
||||
|
|
|
|||
|
|
@ -13,7 +13,7 @@ People can install your extension by typing `docker extension install my/awesome
|
|||
|
||||
However, this option doesn't provide a preview of the extension before it's installed.
|
||||
|
||||
## Createa a share URL
|
||||
## Create a share URL
|
||||
|
||||
Docker lets you share your extensions using a URL.
|
||||
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@
|
|||
title: Image details view
|
||||
keywords: scout, supply chain, vulnerabilities, packages, cves, image, tag, scan,
|
||||
analysis, analyze
|
||||
description: The Docker Scout image detail view analyzes images to show their heirachy,
|
||||
description: The Docker Scout image detail view analyzes images to show their hierarchy,
|
||||
layers, packages, and vulnerabilities
|
||||
aliases:
|
||||
- /scout/image-details-view
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@
|
|||
title: Docker Scout metrics exporter
|
||||
description: |
|
||||
Learn how to scrape data from Docker Scout using Prometheus to create your own
|
||||
vulnerability and policy dashboards wiht Grafana
|
||||
vulnerability and policy dashboards with Grafana
|
||||
keywords: scout, exporter, prometheus, grafana, metrics, dashboard, api, compose
|
||||
aliases:
|
||||
- /scout/metrics-exporter/
|
||||
|
|
|
|||
|
|
@ -82,7 +82,7 @@ grid_resources:
|
|||
description: Understand the steps you can take to improve the security of your container.
|
||||
icon: category
|
||||
link: /develop/security-best-practices/
|
||||
- title: Supress CVEs with VEX
|
||||
- title: Suppress CVEs with VEX
|
||||
description: Learn how to suppress non-applicable or fixed vulnerabilities found in your images.
|
||||
icon: query_stats
|
||||
link: /scout/guides/vex/
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
description: Find the answers to container security related FAQs
|
||||
keywords: Docker, Docker Hub, Docker Desktop secuirty FAQs, platform, Docker Scout, admin, security
|
||||
keywords: Docker, Docker Hub, Docker Desktop security FAQs, platform, Docker Scout, admin, security
|
||||
title: Container security FAQs
|
||||
linkTitle: Container
|
||||
weight: 20
|
||||
|
|
|
|||
|
|
@ -164,7 +164,7 @@ The external namespace to use to set up these attributes is `urn:ietf:params:sci
|
|||
1. Go to **Directory > People > YOUR GROUP > Applications > YOUR APPLICATION**, then select the **Edit** icon.
|
||||
2. Update the attributes to the desired values.
|
||||
|
||||
If a user doesn't already have attributes set up, users who are added to the group will inherit these attributes upon provsioning.
|
||||
If a user doesn't already have attributes set up, users who are added to the group will inherit these attributes upon provisioning.
|
||||
|
||||
{{< /tab >}}
|
||||
{{< tab name="Entra ID SAML 2.0" >}}
|
||||
|
|
|
|||
Loading…
Reference in New Issue