mirror of https://github.com/docker/docs.git
hugo: move manuals content to /manuals section
Signed-off-by: David Karlsson <35727626+dvdksn@users.noreply.github.com>
This commit is contained in:
David Karlsson
parent
b65c890150
commit
135870fc13
|
|
@ -50,8 +50,8 @@ USER root
|
|||
RUN --mount=type=bind,target=. \
|
||||
/usr/local/bin/markdownlint-cli2 \
|
||||
"content/**/*.md" \
|
||||
"#content/engine/release-notes/*.md" \
|
||||
"#content/desktop/previous-versions/*.md"
|
||||
"#content/manuals/engine/release-notes/*.md" \
|
||||
"#content/manuals/desktop/previous-versions/*.md"
|
||||
|
||||
# test validates HTML output and checks for broken links
|
||||
FROM wjdp/htmltest:v${HTMLTEST_VERSION} AS test
|
||||
|
|
|
|||
|
|
@ -106,7 +106,7 @@ Docker API. The Docker client can communicate with more than one daemon.
|
|||
|
||||
### Docker Desktop
|
||||
|
||||
Docker Desktop is an easy-to-install application for your Mac, Windows or Linux environment that enables you to build and share containerized applications and microservices. Docker Desktop includes the Docker daemon (`dockerd`), the Docker client (`docker`), Docker Compose, Docker Content Trust, Kubernetes, and Credential Helper. For more information, see [Docker Desktop](/desktop/index.md).
|
||||
Docker Desktop is an easy-to-install application for your Mac, Windows or Linux environment that enables you to build and share containerized applications and microservices. Docker Desktop includes the Docker daemon (`dockerd`), the Docker client (`docker`), Docker Compose, Docker Content Trust, Kubernetes, and Credential Helper. For more information, see [Docker Desktop](/manuals/desktop/index.md).
|
||||
|
||||
### Docker registries
|
||||
|
||||
|
|
|
|||
|
|
@ -80,7 +80,7 @@ new instance that has never seen this container image. To do this, you will use
|
|||
> $ docker build --platform linux/amd64 -t YOUR-USER-NAME/getting-started .
|
||||
> ```
|
||||
>
|
||||
> Docker buildx also supports building multi-platform images. To learn more, see [Multi-platform images](/build/building/multi-platform.md).
|
||||
> Docker buildx also supports building multi-platform images. To learn more, see [Multi-platform images](/manuals/build/building/multi-platform.md).
|
||||
|
||||
|
||||
1. Open your browser to [Play with Docker](https://labs.play-with-docker.com/).
|
||||
|
|
@ -112,7 +112,7 @@ new instance that has never seen this container image. To do this, you will use
|
|||
> on all interfaces of the host, making it available to the outside world.
|
||||
>
|
||||
> For more information about how port mapping works, see
|
||||
> [Networking](/engine/network/_index.md#published-ports).
|
||||
> [Networking](/manuals/engine/network/_index.md#published-ports).
|
||||
|
||||
6. Select the 3000 badge when it appears.
|
||||
|
||||
|
|
@ -129,8 +129,8 @@ can use the latest version of the image.
|
|||
Related information:
|
||||
|
||||
- [docker CLI reference](/reference/cli/docker/)
|
||||
- [Multi-platform images](/build/building/multi-platform.md)
|
||||
- [Docker Hub overview](/docker-hub/_index.md)
|
||||
- [Multi-platform images](/manuals/build/building/multi-platform.md)
|
||||
- [Docker Hub overview](/manuals/docker-hub/_index.md)
|
||||
|
||||
## Next steps
|
||||
|
||||
|
|
|
|||
|
|
@ -63,7 +63,7 @@ With the previous experiment, you saw that each container starts from the image
|
|||
While containers can create, update, and delete files, those changes are lost when you remove the container
|
||||
and Docker isolates all changes to that container. With volumes, you can change all of this.
|
||||
|
||||
[Volumes](/engine/storage/volumes.md) provide the ability to connect specific filesystem paths of
|
||||
[Volumes](/manuals/engine/storage/volumes.md) provide the ability to connect specific filesystem paths of
|
||||
the container back to the host machine. If you mount a directory in the container, changes in that
|
||||
directory are also seen on the host machine. If you mount that same directory across container restarts, you'd see
|
||||
the same files.
|
||||
|
|
@ -118,7 +118,7 @@ You can create the volume and start the container using the CLI or Docker Deskto
|
|||
> ```
|
||||
>
|
||||
> For more details about Git Bash's syntax differences, see
|
||||
> [Working with Git Bash](../../desktop/troubleshoot/topics/#working-with-git-bash).
|
||||
> [Working with Git Bash](/desktop/troubleshoot/topics/#working-with-git-bash).
|
||||
|
||||
|
||||
{{< /tab >}}
|
||||
|
|
@ -205,7 +205,7 @@ In this section, you learned how to persist container data.
|
|||
Related information:
|
||||
|
||||
- [docker CLI reference](/reference/cli/docker/)
|
||||
- [Volumes](/engine/storage/volumes.md)
|
||||
- [Volumes](/manuals/engine/storage/volumes.md)
|
||||
|
||||
## Next steps
|
||||
|
||||
|
|
|
|||
|
|
@ -49,9 +49,9 @@ work.
|
|||
1. Verify that your `getting-started-app` directory is in a directory defined in
|
||||
Docker Desktop's file sharing setting. This setting defines which parts of your
|
||||
filesystem you can share with containers. For details about accessing the
|
||||
setting, see the topic for [Mac](/desktop/settings/mac.md#file-sharing),
|
||||
[Windows](/desktop/settings/windows.md#file-sharing), or
|
||||
[Linux](/desktop/settings/linux.md#file-sharing).
|
||||
setting, see the topic for [Mac](/manuals/desktop/settings/mac.md#file-sharing),
|
||||
[Windows](/manuals/desktop/settings/windows.md#file-sharing), or
|
||||
[Linux](/manuals/desktop/settings/linux.md#file-sharing).
|
||||
|
||||
2. Open a terminal and change directory to the `getting-started-app`
|
||||
directory.
|
||||
|
|
|
|||
|
|
@ -313,7 +313,7 @@ container. You learned a little bit about container networking and service disco
|
|||
|
||||
Related information:
|
||||
- [docker CLI reference](/reference/cli/docker/)
|
||||
- [Networking overview](/engine/network/_index.md)
|
||||
- [Networking overview](/manuals/engine/network/_index.md)
|
||||
|
||||
## Next steps
|
||||
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ aliases:
|
|||
- /guides/workshop/08_using_compose/
|
||||
---
|
||||
|
||||
[Docker Compose](/compose/_index.md) is a tool that helps you define and
|
||||
[Docker Compose](/manuals/compose/_index.md) is a tool that helps you define and
|
||||
share multi-container applications. With Compose, you can create a YAML file to define the services
|
||||
and with a single command, you can spin everything up or tear it all down.
|
||||
|
||||
|
|
@ -279,7 +279,7 @@ In this section, you learned about Docker Compose and how it helps you simplify
|
|||
the way you define and share multi-service applications.
|
||||
|
||||
Related information:
|
||||
- [Compose overview](/compose/_index.md)
|
||||
- [Compose overview](/manuals/compose/_index.md)
|
||||
- [Compose file reference](/reference/compose-file/_index.md)
|
||||
- [Compose CLI reference](/reference/cli/docker/compose/_index.md)
|
||||
|
||||
|
|
|
|||
|
|
@ -201,7 +201,7 @@ In this section, you learned a few image building best practices, including laye
|
|||
|
||||
Related information:
|
||||
- [Dockerfile reference](/reference/dockerfile/)
|
||||
- [Dockerfile best practices](/build/building/best-practices.md)
|
||||
- [Dockerfile best practices](/manuals/build/building/best-practices.md)
|
||||
|
||||
## Next steps
|
||||
|
||||
|
|
|
|||
|
|
@ -103,8 +103,8 @@ In addition to deploying to Swarm, you've also described your application as a s
|
|||
|
||||
Further documentation for all new Swarm objects and CLI commands used in this article are available here:
|
||||
|
||||
- [Swarm Mode](/engine/swarm/_index.md)
|
||||
- [Swarm Mode Services](/engine/swarm/how-swarm-mode-works/services.md)
|
||||
- [Swarm Stacks](/engine/swarm/stack-deploy.md)
|
||||
- [Swarm Mode](/manuals/engine/swarm/_index.md)
|
||||
- [Swarm Mode Services](/manuals/engine/swarm/how-swarm-mode-works/services.md)
|
||||
- [Swarm Stacks](/manuals/engine/swarm/stack-deploy.md)
|
||||
- [`docker stack *`](/reference/cli/docker/stack/)
|
||||
- [`docker service *`](/reference/cli/docker/service/)
|
||||
|
|
|
|||
|
|
@ -8,9 +8,9 @@ description: Learn how to containerize a generative AI (GenAI) application.
|
|||
|
||||
> [!NOTE]
|
||||
>
|
||||
> GenAI applications can often benefit from GPU acceleration. Currently Docker Desktop supports GPU acceleration only on [Windows with the WSL2 backend](../../../desktop/gpu.md#using-nvidia-gpus-with-wsl2). Linux users can also access GPU acceleration using a native installation of the [Docker Engine](../../../engine/install/_index.md).
|
||||
> GenAI applications can often benefit from GPU acceleration. Currently Docker Desktop supports GPU acceleration only on [Windows with the WSL2 backend](/manuals/desktop/gpu.md#using-nvidia-gpus-with-wsl2). Linux users can also access GPU acceleration using a native installation of the [Docker Engine](/manuals/engine/install/_index.md).
|
||||
|
||||
* You have installed the latest version of [Docker Desktop](/get-started/get-docker.md) or, if you are a Linux user and are planning to use GPU acceleration, [Docker Engine](../../../engine/install/_index.md). Docker adds new features regularly and some parts of this guide may work only with the latest version of Docker Desktop.
|
||||
* You have installed the latest version of [Docker Desktop](/get-started/get-docker.md) or, if you are a Linux user and are planning to use GPU acceleration, [Docker Engine](/manuals/engine/install/_index.md). Docker adds new features regularly and some parts of this guide may work only with the latest version of Docker Desktop.
|
||||
* You have a [git client](https://git-scm.com/downloads). The examples in this section use a command-line based git client, but you can use any client.
|
||||
|
||||
## Overview
|
||||
|
|
|
|||
|
|
@ -99,7 +99,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 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](../../../desktop/wsl/index.md/#turn-on-docker-desktop-wsl-2)
|
||||
- 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`:
|
||||
|
||||
|
|
@ -146,7 +146,7 @@ To run Ollama in a container and provide GPU access:
|
|||
|
||||
> [!NOTE]
|
||||
>
|
||||
> For more details about the Compose instructions, see [Turn on GPU access with Docker Compose](../../../compose/gpu-support.md).
|
||||
> For more details about the Compose instructions, see [Turn on GPU access with Docker Compose](/manuals/compose/gpu-support.md).
|
||||
|
||||
3. Add the ollama-pull service to your `compose.yaml` file. This service uses
|
||||
the `docker/genai:ollama-pull` image, based on the GenAI Stack's
|
||||
|
|
|
|||
|
|
@ -183,7 +183,7 @@ underlying system differences. To learn more about Docker, see the [Getting star
|
|||
|
||||
Docker Compose is a tool for defining and running multi-container applications.
|
||||
Compose makes it easy to run this application with a single command, `docker
|
||||
compose up`. For more details, see the [Compose overview](../../../compose/_index.md).
|
||||
compose up`. For more details, see the [Compose overview](/manuals/compose/_index.md).
|
||||
|
||||
### OpenAI API
|
||||
|
||||
|
|
|
|||
|
|
@ -371,7 +371,7 @@ $ docker run --rm -p 8889:8888 YOUR-USER-NAME/my-jupyer-image start-notebook.py
|
|||
|
||||
### Share your volume
|
||||
|
||||
This example uses the Docker Desktop [Volumes Backup & Share](https://hub.docker.com/extensions/docker/volumes-backup-extension) extension. Alternatively, in the CLI you can [back up the volume](/engine/storage/volumes/#back-up-a-volume) and then [push it using the ORAS CLI](/docker-hub/oci-artifacts/#push-a-volume).
|
||||
This example uses the Docker Desktop [Volumes Backup & Share](https://hub.docker.com/extensions/docker/volumes-backup-extension) extension. Alternatively, in the CLI you can [back up the volume](/engine/storage/volumes/#back-up-a-volume) and then [push it using the ORAS CLI](/manuals/docker-hub/oci-artifacts.md#push-a-volume).
|
||||
|
||||
1. Install the Volumes Backup & Share extension.
|
||||
1. Open the Docker Dashboard and select **Extensions**.
|
||||
|
|
|
|||
|
|
@ -431,7 +431,7 @@ Docker Compose is a tool for defining and running multi-container Docker
|
|||
applications. With Compose, you use a YAML file to configure your application's
|
||||
services, networks, and volumes. In this case, the application isn't a
|
||||
multi-container application, but Docker Compose has other useful features for
|
||||
development, like [Compose Watch](../../compose/file-watch.md).
|
||||
development, like [Compose Watch](/manuals/compose/file-watch.md).
|
||||
|
||||
The sample application doesn't have a Compose file yet. To create a Compose
|
||||
file, in the `TensorJS-Face-Detection` directory, create a text file named
|
||||
|
|
|
|||
|
|
@ -2,5 +2,5 @@
|
|||
---
|
||||
|
||||
{{% experimental %}}
|
||||
Compose Bridge is an [Experimental](/release-lifecycle.md#experimental) product.
|
||||
Compose Bridge is an [Experimental](/manuals/release-lifecycle.md#experimental) product.
|
||||
{{% /experimental %}}
|
||||
|
|
|
|||
|
|
@ -16,8 +16,8 @@ The language-specific guides walk you through the process of:
|
|||
|
||||
In addition to the language-specific modules, Docker documentation also provides guidelines to build images and efficiently manage your development environment. For more information, refer to the following topics:
|
||||
|
||||
* [Building best practices](../build/building/best-practices.md)
|
||||
* [Build images with BuildKit](../build/buildkit/index.md#getting-started)
|
||||
* [Building best practices](/manuals/build/building/best-practices.md)
|
||||
* [Build images with BuildKit](/manuals/build/buildkit/index.md#getting-started)
|
||||
|
||||
## Language-specific guides
|
||||
|
||||
|
|
|
|||
|
|
@ -27,7 +27,7 @@ Create a GitHub repository, configure the Docker Hub credentials, and push your
|
|||
|
||||
3. Create a new **Repository variable** named `DOCKER_USERNAME` and your Docker ID as value.
|
||||
|
||||
4. Create a new [Personal Access Token (PAT)](../../security/for-developers/access-tokens.md/#create-an-access-token) for Docker Hub. You can name this token `docker-tutorial`. Make sure access permissions include Read and Write.
|
||||
4. Create a new [Personal Access Token (PAT)](/manuals/security/for-developers/access-tokens.md#create-an-access-token) for Docker Hub. You can name this token `docker-tutorial`. Make sure access permissions include Read and Write.
|
||||
|
||||
5. Add the PAT as a **Repository secret** in your GitHub repository, with the name
|
||||
`DOCKERHUB_TOKEN`.
|
||||
|
|
@ -119,7 +119,7 @@ Save the workflow file and run the job.
|
|||
In this section, you learned how to set up a GitHub Actions workflow for your C++ application.
|
||||
|
||||
Related information:
|
||||
- [Introduction to GitHub Actions](../../build/ci/github-actions/_index.md)
|
||||
- [Introduction to GitHub Actions](/manuals/build/ci/github-actions/_index.md)
|
||||
- [Workflow syntax for GitHub Actions](https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions)
|
||||
|
||||
## Next steps
|
||||
|
|
|
|||
|
|
@ -79,7 +79,7 @@ In this section, you learned how you can containerize and run your C++
|
|||
application using Docker.
|
||||
|
||||
Related information:
|
||||
- [Docker Compose overview](../../compose/_index.md)
|
||||
- [Docker Compose overview](/manuals/compose/_index.md)
|
||||
|
||||
## Next steps
|
||||
|
||||
|
|
|
|||
|
|
@ -133,5 +133,5 @@ In this section, you learned how to use Docker Desktop to deploy your C++ applic
|
|||
|
||||
Related information:
|
||||
- [Kubernetes documentation](https://kubernetes.io/docs/home/)
|
||||
- [Deploy on Kubernetes with Docker Desktop](../../desktop/kubernetes.md)
|
||||
- [Swarm mode overview](../../engine/swarm/_index.md)
|
||||
- [Deploy on Kubernetes with Docker Desktop](/manuals/desktop/kubernetes.md)
|
||||
- [Swarm mode overview](/manuals/engine/swarm/_index.md)
|
||||
|
|
|
|||
|
|
@ -26,7 +26,7 @@ $ git clone https://github.com/Pradumnasaraf/c-plus-plus-docker.git
|
|||
|
||||
Use Compose Watch to automatically update your running Compose services as you
|
||||
edit and save your code. For more details about Compose Watch, see [Use Compose
|
||||
Watch](../../compose/file-watch.md).
|
||||
Watch](/manuals/compose/file-watch.md).
|
||||
|
||||
Open your `compose.yml` file in an IDE or text editor and then add the Compose Watch instructions. The following example shows how to add Compose Watch to your `compose.yml` file.
|
||||
|
||||
|
|
@ -63,8 +63,8 @@ In this section, you also learned how to use Compose Watch to automatically rebu
|
|||
|
||||
Related information:
|
||||
- [Compose file reference](/reference/compose-file/)
|
||||
- [Compose file watch](../../compose/file-watch.md)
|
||||
- [Multi-stage builds](../../build/building/multi-stage.md)
|
||||
- [Compose file watch](/manuals/compose/file-watch.md)
|
||||
- [Multi-stage builds](/manuals/build/building/multi-stage.md)
|
||||
|
||||
## Next steps
|
||||
|
||||
|
|
|
|||
|
|
@ -27,7 +27,7 @@ Create a GitHub repository, configure the Docker Hub credentials, and push your
|
|||
|
||||
3. Create a new **Repository variable** named `DOCKER_USERNAME` and your Docker ID as value.
|
||||
|
||||
4. Create a new [Personal Access Token (PAT)](../../security/for-developers/access-tokens.md/#create-an-access-token) for Docker Hub. You can name this token `docker-tutorial`. Make sure access permissions include Read and Write.
|
||||
4. Create a new [Personal Access Token (PAT)](/manuals/security/for-developers/access-tokens.md#create-an-access-token) for Docker Hub. You can name this token `docker-tutorial`. Make sure access permissions include Read and Write.
|
||||
|
||||
5. Add the PAT as a **Repository secret** in your GitHub repository, with the name
|
||||
`DOCKERHUB_TOKEN`.
|
||||
|
|
@ -134,7 +134,7 @@ Save the workflow file and run the job.
|
|||
In this section, you learned how to set up a GitHub Actions workflow for your application.
|
||||
|
||||
Related information:
|
||||
- [Introduction to GitHub Actions](../../build/ci/github-actions/_index.md)
|
||||
- [Introduction to GitHub Actions](/manuals/build/ci/github-actions/_index.md)
|
||||
- [Workflow syntax for GitHub Actions](https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions)
|
||||
|
||||
## Next steps
|
||||
|
|
|
|||
|
|
@ -121,7 +121,7 @@ application using Docker.
|
|||
Related information:
|
||||
- [Dockerfile reference](../../reference/dockerfile.md)
|
||||
- [.dockerignore file reference](../../reference/dockerfile.md#dockerignore-file)
|
||||
- [Docker Compose overview](../../compose/_index.md)
|
||||
- [Docker Compose overview](/manuals/compose/_index.md)
|
||||
|
||||
## Next steps
|
||||
|
||||
|
|
|
|||
|
|
@ -209,5 +209,5 @@ In this section, you learned how to use Docker Desktop to deploy your applicatio
|
|||
|
||||
Related information:
|
||||
- [Kubernetes documentation](https://kubernetes.io/docs/home/)
|
||||
- [Deploy on Kubernetes with Docker Desktop](../../desktop/kubernetes.md)
|
||||
- [Swarm mode overview](../../engine/swarm/_index.md)
|
||||
- [Deploy on Kubernetes with Docker Desktop](/manuals/desktop/kubernetes.md)
|
||||
- [Swarm mode overview](/manuals/engine/swarm/_index.md)
|
||||
|
|
|
|||
|
|
@ -225,7 +225,7 @@ Press `ctrl+c` in the terminal to stop your application.
|
|||
|
||||
## Automatically update services
|
||||
|
||||
Use Compose Watch to automatically update your running Compose services as you edit and save your code. For more details about Compose Watch, see [Use Compose Watch](../../compose/file-watch.md).
|
||||
Use Compose Watch to automatically update your running Compose services as you edit and save your code. For more details about Compose Watch, see [Use Compose Watch](/manuals/compose/file-watch.md).
|
||||
|
||||
Open your `compose.yaml` file in an IDE or text editor and then add the Compose Watch instructions. The following is the updated `compose.yaml` file.
|
||||
|
||||
|
|
@ -292,7 +292,7 @@ Press `ctrl+c` in the terminal to stop your application.
|
|||
|
||||
## Create a development container
|
||||
|
||||
At this point, when you run your containerized application, it's using the .NET runtime image. While this small image is good for production, it lacks the SDK tools and dependencies you may need when developing. Also, during development, you may not need to run `dotnet publish`. You can use multi-stage builds to build stages for both development and production in the same Dockerfile. For more details, see [Multi-stage builds](../../build/building/multi-stage.md).
|
||||
At this point, when you run your containerized application, it's using the .NET runtime image. While this small image is good for production, it lacks the SDK tools and dependencies you may need when developing. Also, during development, you may not need to run `dotnet publish`. You can use multi-stage builds to build stages for both development and production in the same Dockerfile. For more details, see [Multi-stage builds](/manuals/build/building/multi-stage.md).
|
||||
|
||||
Add a new development stage to your Dockerfile and update your `compose.yaml` file to use this stage for local development.
|
||||
|
||||
|
|
@ -383,8 +383,8 @@ database and persist data. You also learned how to use Compose Watch to automati
|
|||
|
||||
Related information:
|
||||
- [Compose file reference](/reference/compose-file/)
|
||||
- [Compose file watch](../../compose/file-watch.md)
|
||||
- [Multi-stage builds](../../build/building/multi-stage.md)
|
||||
- [Compose file watch](/manuals/compose/file-watch.md)
|
||||
- [Multi-stage builds](/manuals/build/building/multi-stage.md)
|
||||
|
||||
## Next steps
|
||||
|
||||
|
|
|
|||
|
|
@ -30,11 +30,11 @@ the [Go website](https://golang.org/) is a great place to explore,
|
|||
so *go* (pun intended) check it out!
|
||||
|
||||
You also must know some basic [Docker concepts](/get-started/docker-concepts/the-basics/what-is-a-container.md) as well as to
|
||||
be at least vaguely familiar with the [Dockerfile format](../../build/concepts/dockerfile.md).
|
||||
be at least vaguely familiar with the [Dockerfile format](/manuals/build/concepts/dockerfile.md).
|
||||
|
||||
Your Docker set-up must have BuildKit enabled. BuildKit is enabled by default for all users on [Docker Desktop](../../desktop/index.md).
|
||||
Your Docker set-up must have BuildKit enabled. BuildKit is enabled by default for all users on [Docker Desktop](/manuals/desktop/index.md).
|
||||
If you have installed Docker Desktop, you don’t have to manually enable BuildKit. If you are running Docker on Linux,
|
||||
please check out BuildKit [getting started](../../build/buildkit/index.md#getting-started) page.
|
||||
please check out BuildKit [getting started](/manuals/build/buildkit/index.md#getting-started) page.
|
||||
|
||||
Some familiarity with the command line is also expected.
|
||||
|
||||
|
|
|
|||
|
|
@ -17,7 +17,7 @@ application.
|
|||
|
||||
To complete this tutorial, you need the following:
|
||||
|
||||
- Docker running locally. Follow the [instructions to download and install Docker](../../desktop/index.md).
|
||||
- Docker running locally. Follow the [instructions to download and install Docker](/manuals/desktop/index.md).
|
||||
- An IDE or a text editor to edit files. [Visual Studio Code](https://code.visualstudio.com/) is a free and popular choice but you can use anything you feel comfortable with.
|
||||
- A Git client. This guide uses a command-line based `git` client, but you are free to use whatever works for you.
|
||||
- A command-line terminal application. The examples shown in this module are from the Linux shell, but they should work in PowerShell, Windows Command Prompt, or OS X Terminal with minimal, if any, modifications.
|
||||
|
|
@ -113,7 +113,7 @@ has all necessary tools and libraries to compile and run a Go application.
|
|||
|
||||
> [!NOTE]
|
||||
>
|
||||
> If you are curious about creating your own base images, you can check out the following section of this guide: [creating base images](../../build/building/base-images.md#create-a-base-image).
|
||||
> If you are curious about creating your own base images, you can check out the following section of this guide: [creating base images](/manuals/build/building/base-images.md#create-a-base-image).
|
||||
> Note, however, that this isn't necessary to continue with your task at hand.
|
||||
|
||||
Now that you have defined the base image for your upcoming container image, you
|
||||
|
|
@ -307,7 +307,7 @@ successfully built your image named `docker-gs-ping`.
|
|||
|
||||
To see the list of images you have on your local machine, you have two options.
|
||||
One is to use the CLI and the other is to use [Docker
|
||||
Desktop](../../desktop/index.md). Since you're currently working in the
|
||||
Desktop](/manuals/desktop/index.md). Since you're currently working in the
|
||||
terminal, take a look at listing images with the CLI.
|
||||
|
||||
To list images, run the `docker image ls`command (or the `docker images` shorthand):
|
||||
|
|
@ -407,7 +407,7 @@ The answer is that the full toolchain is still there, in the container image.
|
|||
Not only this is inconvenient because of the large file size, but it may also
|
||||
present a security risk when the container is deployed.
|
||||
|
||||
These two issues can be solved by using [multi-stage builds](../../build/building/multi-stage.md).
|
||||
These two issues can be solved by using [multi-stage builds](/manuals/build/building/multi-stage.md).
|
||||
|
||||
In a nutshell, a multi-stage build can carry over the artifacts from one build stage into another,
|
||||
and every build stage can be instantiated from a different base image.
|
||||
|
|
@ -478,7 +478,7 @@ This is so because the ["distroless"](https://github.com/GoogleContainerTools/di
|
|||
base image that you have used in the second stage of the build is very barebones and is designed for lean deployments of static binaries.
|
||||
|
||||
There's much more to multi-stage builds, including the possibility of multi-architecture builds,
|
||||
so feel free to check out [multi-stage builds](../../build/building/multi-stage.md). This is, however, not essential for your progress here.
|
||||
so feel free to check out [multi-stage builds](/manuals/build/building/multi-stage.md). This is, however, not essential for your progress here.
|
||||
|
||||
## Next steps
|
||||
|
||||
|
|
|
|||
|
|
@ -27,7 +27,7 @@ Create a GitHub repository, configure the Docker Hub credentials, and push your
|
|||
|
||||
3. Create a new **Repository variable** named `DOCKER_USERNAME` and your Docker ID as value.
|
||||
|
||||
4. Create a new [Personal Access Token (PAT)](../../security/for-developers/access-tokens.md/#create-an-access-token) for Docker Hub. You can name this token `docker-tutorial`. Make sure access permissions include Read and Write.
|
||||
4. Create a new [Personal Access Token (PAT)](/manuals/security/for-developers/access-tokens.md#create-an-access-token) for Docker Hub. You can name this token `docker-tutorial`. Make sure access permissions include Read and Write.
|
||||
|
||||
5. Add the PAT as a **Repository secret** in your GitHub repository, with the name
|
||||
`DOCKERHUB_TOKEN`.
|
||||
|
|
@ -119,7 +119,7 @@ Save the workflow file and run the job.
|
|||
In this section, you learned how to set up a GitHub Actions workflow for your application.
|
||||
|
||||
Related information:
|
||||
- [Introduction to GitHub Actions](../../build/ci/github-actions/_index.md)
|
||||
- [Introduction to GitHub Actions](/manuals/build/ci/github-actions/_index.md)
|
||||
- [Workflow syntax for GitHub Actions](https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions)
|
||||
|
||||
## Next steps
|
||||
|
|
|
|||
|
|
@ -234,5 +234,5 @@ In this section, you learned how to use Docker Desktop to deploy your applicatio
|
|||
|
||||
Related information:
|
||||
- [Kubernetes documentation](https://kubernetes.io/docs/home/)
|
||||
- [Deploy on Kubernetes with Docker Desktop](../../desktop/kubernetes.md)
|
||||
- [Swarm mode overview](../../engine/swarm/_index.md)
|
||||
- [Deploy on Kubernetes with Docker Desktop](/manuals/desktop/kubernetes.md)
|
||||
- [Swarm mode overview](/manuals/engine/swarm/_index.md)
|
||||
|
|
|
|||
|
|
@ -26,7 +26,7 @@ For more information on the relation between Go and CockroachDB, refer to the [C
|
|||
|
||||
### Storage
|
||||
|
||||
The point of a database is to have a persistent store of data. [Volumes](/engine/storage/volumes.md) are the preferred mechanism for persisting data generated by and used by Docker containers. Thus, before you start CockroachDB, create the volume for it.
|
||||
The point of a database is to have a persistent store of data. [Volumes](/manuals/engine/storage/volumes.md) are the preferred mechanism for persisting data generated by and used by Docker containers. Thus, before you start CockroachDB, create the volume for it.
|
||||
|
||||
To create a managed volume, run :
|
||||
|
||||
|
|
@ -65,7 +65,7 @@ daed20bbecce host host local
|
|||
6aee44f40a39 none null local
|
||||
```
|
||||
|
||||
Your bridge network `mynet` has been created successfully. The other three networks, named `bridge`, `host`, and `none` are the default networks and they had been created by the Docker itself. While it's not relevant to this guide, you can learn more about Docker networking in the [networking overview](/engine/network/_index.md) section.
|
||||
Your bridge network `mynet` has been created successfully. The other three networks, named `bridge`, `host`, and `none` are the default networks and they had been created by the Docker itself. While it's not relevant to this guide, you can learn more about Docker networking in the [networking overview](/manuals/engine/network/_index.md) section.
|
||||
|
||||
### Choose good names for volumes and networks
|
||||
|
||||
|
|
@ -568,7 +568,7 @@ networks:
|
|||
```
|
||||
|
||||
|
||||
This Docker Compose configuration is super convenient as you don't have to type all the parameters to pass to the `docker run` command. You can declaratively do that in the Docker Compose file. The [Docker Compose documentation pages](../../compose/index.md) are quite extensive and include a full reference for the Docker Compose file format.
|
||||
This Docker Compose configuration is super convenient as you don't have to type all the parameters to pass to the `docker run` command. You can declaratively do that in the Docker Compose file. The [Docker Compose documentation pages](/manuals/compose/index.md) are quite extensive and include a full reference for the Docker Compose file format.
|
||||
|
||||
### The `.env` file
|
||||
|
||||
|
|
@ -711,7 +711,7 @@ There are some tangential, yet interesting points that were purposefully not cov
|
|||
|
||||
### Persistent storage
|
||||
|
||||
A managed volume isn't the only way to provide your container with persistent storage. It is highly recommended to get acquainted with available storage options and their use cases, covered in [Manage data in Docker](/engine/storage/_index.md).
|
||||
A managed volume isn't the only way to provide your container with persistent storage. It is highly recommended to get acquainted with available storage options and their use cases, covered in [Manage data in Docker](/manuals/engine/storage/_index.md).
|
||||
|
||||
### CockroachDB clusters
|
||||
|
||||
|
|
|
|||
|
|
@ -27,7 +27,7 @@ Create a GitHub repository, configure the Docker Hub credentials, and push your
|
|||
|
||||
3. Create a new **Repository variable** named `DOCKER_USERNAME` and your Docker ID as value.
|
||||
|
||||
4. Create a new [Personal Access Token (PAT)](../../security/for-developers/access-tokens.md/#create-an-access-token) for Docker Hub. You can name this token `docker-tutorial`. Make sure access permissions include Read and Write.
|
||||
4. Create a new [Personal Access Token (PAT)](/manuals/security/for-developers/access-tokens.md#create-an-access-token) for Docker Hub. You can name this token `docker-tutorial`. Make sure access permissions include Read and Write.
|
||||
|
||||
5. Add the PAT as a **Repository secret** in your GitHub repository, with the name
|
||||
`DOCKERHUB_TOKEN`.
|
||||
|
|
@ -129,7 +129,7 @@ Save the workflow file and run the job.
|
|||
In this section, you learned how to set up a GitHub Actions workflow for your application.
|
||||
|
||||
Related information:
|
||||
- [Introduction to GitHub Actions](../../build/ci/github-actions/_index.md)
|
||||
- [Introduction to GitHub Actions](/manuals/build/ci/github-actions/_index.md)
|
||||
- [Workflow syntax for GitHub Actions](https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions)
|
||||
|
||||
## Next steps
|
||||
|
|
|
|||
|
|
@ -144,5 +144,5 @@ In this section, you learned how to use Docker Desktop to deploy your applicatio
|
|||
|
||||
Related information:
|
||||
- [Kubernetes documentation](https://kubernetes.io/docs/home/)
|
||||
- [Deploy on Kubernetes with Docker Desktop](../../desktop/kubernetes.md)
|
||||
- [Swarm mode overview](../../engine/swarm/_index.md)
|
||||
- [Deploy on Kubernetes with Docker Desktop](/manuals/desktop/kubernetes.md)
|
||||
- [Swarm mode overview](/manuals/engine/swarm/_index.md)
|
||||
|
|
|
|||
|
|
@ -261,7 +261,7 @@ Press `ctrl+c` in the terminal to stop your application.
|
|||
|
||||
Use Compose Watch to automatically update your running Compose services as you
|
||||
edit and save your code. For more details about Compose Watch, see
|
||||
[Use Compose Watch](../../compose/file-watch.md).
|
||||
[Use Compose Watch](/manuals/compose/file-watch.md).
|
||||
|
||||
Open your `docker-compose.yaml` file in an IDE or text editor and then add the
|
||||
Compose Watch instructions. The following is the updated `docker-compose.yaml`
|
||||
|
|
@ -336,7 +336,7 @@ In this section, you took a look at running a database locally and persisting th
|
|||
Related information:
|
||||
|
||||
- [Compose file reference](/reference/compose-file/)
|
||||
- [Compose Watch](../../compose/file-watch.md)
|
||||
- [Compose Watch](/manuals/compose/file-watch.md)
|
||||
- [Dockerfile reference](/reference/dockerfile/)
|
||||
|
||||
## Next steps
|
||||
|
|
|
|||
|
|
@ -27,7 +27,7 @@ Create a GitHub repository, configure the Docker Hub credentials, and push your
|
|||
|
||||
3. Create a new **Repository variable** named `DOCKER_USERNAME` and your Docker ID as value.
|
||||
|
||||
4. Create a new [Personal Access Token (PAT)](../../security/for-developers/access-tokens.md/#create-an-access-token) for Docker Hub. You can name this token `docker-tutorial`. Make sure access permissions include Read and Write.
|
||||
4. Create a new [Personal Access Token (PAT)](/manuals/security/for-developers/access-tokens.md#create-an-access-token) for Docker Hub. You can name this token `docker-tutorial`. Make sure access permissions include Read and Write.
|
||||
|
||||
5. Add the PAT as a **Repository secret** in your GitHub repository, with the name
|
||||
`DOCKERHUB_TOKEN`.
|
||||
|
|
@ -126,7 +126,7 @@ Save the workflow file and run the job.
|
|||
In this section, you learned how to set up a GitHub Actions workflow for your Node.js application.
|
||||
|
||||
Related information:
|
||||
- [Introduction to GitHub Actions](../../build/ci/github-actions/_index.md)
|
||||
- [Introduction to GitHub Actions](/manuals/build/ci/github-actions/_index.md)
|
||||
- [Workflow syntax for GitHub Actions](https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions)
|
||||
|
||||
## Next steps
|
||||
|
|
|
|||
|
|
@ -276,7 +276,7 @@ application using Docker.
|
|||
Related information:
|
||||
- [Dockerfile reference](../../reference/dockerfile.md)
|
||||
- [.dockerignore file reference](../../reference/dockerfile.md#dockerignore-file)
|
||||
- [Docker Compose overview](../../compose/_index.md)
|
||||
- [Docker Compose overview](/manuals/compose/_index.md)
|
||||
|
||||
## Next steps
|
||||
|
||||
|
|
|
|||
|
|
@ -133,5 +133,5 @@ In this section, you learned how to use Docker Desktop to deploy your applicatio
|
|||
|
||||
Related information:
|
||||
- [Kubernetes documentation](https://kubernetes.io/docs/home/)
|
||||
- [Deploy on Kubernetes with Docker Desktop](../../desktop/kubernetes.md)
|
||||
- [Swarm mode overview](../../engine/swarm/_index.md)
|
||||
- [Deploy on Kubernetes with Docker Desktop](/manuals/desktop/kubernetes.md)
|
||||
- [Swarm mode overview](/manuals/engine/swarm/_index.md)
|
||||
|
|
|
|||
|
|
@ -270,7 +270,7 @@ have these variables defined yet.
|
|||
|
||||
## Configure and run a development container
|
||||
|
||||
You can use a bind mount to mount your source code into the container. The container can then see the changes you make to the code immediately, as soon as you save a file. This means that you can run processes, like nodemon, in the container that watch for filesystem changes and respond to them. To learn more about bind mounts, see [Storage overview](/engine/storage/index.md).
|
||||
You can use a bind mount to mount your source code into the container. The container can then see the changes you make to the code immediately, as soon as you save a file. This means that you can run processes, like nodemon, in the container that watch for filesystem changes and respond to them. To learn more about bind mounts, see [Storage overview](/manuals/engine/storage/index.md).
|
||||
|
||||
In addition to adding a bind mount, you can configure your Dockerfile and `compose.yaml` file to install development dependencies and run development tools.
|
||||
|
||||
|
|
@ -320,7 +320,7 @@ in other build stages. Next, you add a new build stage labeled `dev` to install
|
|||
your development dependencies and start the container using `npm run dev`.
|
||||
Finally, you add a stage labeled `prod` that omits the dev dependencies and runs
|
||||
your application using `node src/index.js`. To learn more about multi-stage
|
||||
builds, see [Multi-stage builds](../../build/building/multi-stage.md).
|
||||
builds, see [Multi-stage builds](/manuals/build/building/multi-stage.md).
|
||||
|
||||
Next, you'll need to update your Compose file to use the new stage.
|
||||
|
||||
|
|
@ -419,7 +419,7 @@ Dockerfile and set up a bind mount for development.
|
|||
Related information:
|
||||
- [Volumes top-level element](/reference/compose-file/volumes/)
|
||||
- [Services top-level element](/reference/compose-file/services/)
|
||||
- [Multi-stage builds](../../build/building/multi-stage.md)
|
||||
- [Multi-stage builds](/manuals/build/building/multi-stage.md)
|
||||
|
||||
## Next steps
|
||||
|
||||
|
|
|
|||
|
|
@ -27,7 +27,7 @@ Create a GitHub repository, configure the Docker Hub credentials, and push your
|
|||
|
||||
3. Create a new **Repository variable** named `DOCKER_USERNAME` and your Docker ID as value.
|
||||
|
||||
4. Create a new [Personal Access Token (PAT)](../../security/for-developers/access-tokens.md/#create-an-access-token) for Docker Hub. You can name this token `docker-tutorial`. Make sure access permissions include Read and Write.
|
||||
4. Create a new [Personal Access Token (PAT)](/manuals/security/for-developers/access-tokens.md#create-an-access-token) for Docker Hub. You can name this token `docker-tutorial`. Make sure access permissions include Read and Write.
|
||||
|
||||
5. Add the PAT as a **Repository secret** in your GitHub repository, with the name
|
||||
`DOCKERHUB_TOKEN`.
|
||||
|
|
@ -134,7 +134,7 @@ Save the workflow file and run the job.
|
|||
In this section, you learned how to set up a GitHub Actions workflow for your application.
|
||||
|
||||
Related information:
|
||||
- [Introduction to GitHub Actions](../../build/ci/github-actions/_index.md)
|
||||
- [Introduction to GitHub Actions](/manuals/build/ci/github-actions/_index.md)
|
||||
- [Workflow syntax for GitHub Actions](https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions)
|
||||
|
||||
## Next steps
|
||||
|
|
|
|||
|
|
@ -136,5 +136,5 @@ In this section, you learned how to use Docker Desktop to deploy your applicatio
|
|||
|
||||
Related information:
|
||||
- [Kubernetes documentation](https://kubernetes.io/docs/home/)
|
||||
- [Deploy on Kubernetes with Docker Desktop](../../desktop/kubernetes.md)
|
||||
- [Swarm mode overview](../../engine/swarm/_index.md)
|
||||
- [Deploy on Kubernetes with Docker Desktop](/manuals/desktop/kubernetes.md)
|
||||
- [Swarm mode overview](/manuals/engine/swarm/_index.md)
|
||||
|
|
|
|||
|
|
@ -236,7 +236,7 @@ Press `ctrl+c` in the terminal to stop your application.
|
|||
|
||||
## Automatically update services
|
||||
|
||||
Use Compose Watch to automatically update your running Compose services as you edit and save your code. For more details about Compose Watch, see [Use Compose Watch](../../compose/file-watch.md).
|
||||
Use Compose Watch to automatically update your running Compose services as you edit and save your code. For more details about Compose Watch, see [Use Compose Watch](/manuals/compose/file-watch.md).
|
||||
|
||||
Open your `compose.yaml` file in an IDE or text editor and then add the Compose Watch instructions. The following is the updated `compose.yaml` file.
|
||||
|
||||
|
|
@ -313,7 +313,7 @@ Press `ctrl+c` in the terminal to stop Compose Watch. Run `docker compose down`
|
|||
|
||||
## Create a development container
|
||||
|
||||
At this point, when you run your containerized application, Composer isn't installing the dev dependencies. While this small image is good for production, it lacks the tools and dependencies you may need when developing and it doesn't include the `tests` directory. You can use multi-stage builds to build stages for both development and production in the same Dockerfile. For more details, see [Multi-stage builds](../../build/building/multi-stage.md).
|
||||
At this point, when you run your containerized application, Composer isn't installing the dev dependencies. While this small image is good for production, it lacks the tools and dependencies you may need when developing and it doesn't include the `tests` directory. You can use multi-stage builds to build stages for both development and production in the same Dockerfile. For more details, see [Multi-stage builds](/manuals/build/building/multi-stage.md).
|
||||
|
||||
In the `Dockerfile`, you'll need to update the following:
|
||||
1. Split the `deps` staged into two stages. One stage for production
|
||||
|
|
@ -418,7 +418,7 @@ database and persist data. You also learned how to use Compose Watch to automati
|
|||
|
||||
Related information:
|
||||
- [Compose file reference](/reference/compose-file/)
|
||||
- [Compose file watch](../../compose/file-watch.md)
|
||||
- [Compose file watch](/manuals/compose/file-watch.md)
|
||||
- [Dockerfile reference](../../reference/dockerfile.md)
|
||||
- [Official Docker Image for PHP](https://hub.docker.com/_/php)
|
||||
|
||||
|
|
|
|||
|
|
@ -27,7 +27,7 @@ Create a GitHub repository, configure the Docker Hub credentials, and push your
|
|||
|
||||
3. Create a new **Repository variable** named `DOCKER_USERNAME` and your Docker ID as value.
|
||||
|
||||
4. Create a new [Personal Access Token (PAT)](../../security/for-developers/access-tokens.md/#create-an-access-token) for Docker Hub. You can name this token `docker-tutorial`. Make sure access permissions include Read and Write.
|
||||
4. Create a new [Personal Access Token (PAT)](/manuals/security/for-developers/access-tokens.md#create-an-access-token) for Docker Hub. You can name this token `docker-tutorial`. Make sure access permissions include Read and Write.
|
||||
|
||||
5. Add the PAT as a **Repository secret** in your GitHub repository, with the name
|
||||
`DOCKERHUB_TOKEN`.
|
||||
|
|
@ -119,7 +119,7 @@ Save the workflow file and run the job.
|
|||
In this section, you learned how to set up a GitHub Actions workflow for your Python application.
|
||||
|
||||
Related information:
|
||||
- [Introduction to GitHub Actions](../../build/ci/github-actions/_index.md)
|
||||
- [Introduction to GitHub Actions](/manuals/build/ci/github-actions/_index.md)
|
||||
- [Workflow syntax for GitHub Actions](https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions)
|
||||
|
||||
## Next steps
|
||||
|
|
|
|||
|
|
@ -364,7 +364,7 @@ In this section, you learned how you can containerize and run your Python
|
|||
application using Docker.
|
||||
|
||||
Related information:
|
||||
- [Docker Compose overview](../../compose/_index.md)
|
||||
- [Docker Compose overview](/manuals/compose/_index.md)
|
||||
|
||||
## Next steps
|
||||
|
||||
|
|
|
|||
|
|
@ -247,5 +247,5 @@ In this section, you learned how to use Docker Desktop to deploy your applicatio
|
|||
|
||||
Related information:
|
||||
- [Kubernetes documentation](https://kubernetes.io/docs/home/)
|
||||
- [Deploy on Kubernetes with Docker Desktop](../../desktop/kubernetes.md)
|
||||
- [Swarm mode overview](../../engine/swarm/_index.md)
|
||||
- [Deploy on Kubernetes with Docker Desktop](/manuals/desktop/kubernetes.md)
|
||||
- [Swarm mode overview](/manuals/engine/swarm/_index.md)
|
||||
|
|
|
|||
|
|
@ -469,7 +469,7 @@ Press `ctrl+c` in the terminal to stop your application.
|
|||
|
||||
Use Compose Watch to automatically update your running Compose services as you
|
||||
edit and save your code. For more details about Compose Watch, see [Use Compose
|
||||
Watch](../../compose/file-watch.md).
|
||||
Watch](/manuals/compose/file-watch.md).
|
||||
|
||||
Open your `compose.yaml` file in an IDE or text editor and then add the Compose
|
||||
Watch instructions. The following is the updated `compose.yaml` file.
|
||||
|
|
@ -558,8 +558,8 @@ database and persist data. You also learned how to use Compose Watch to automati
|
|||
|
||||
Related information:
|
||||
- [Compose file reference](/reference/compose-file/)
|
||||
- [Compose file watch](../../compose/file-watch.md)
|
||||
- [Multi-stage builds](../../build/building/multi-stage.md)
|
||||
- [Compose file watch](/manuals/compose/file-watch.md)
|
||||
- [Multi-stage builds](/manuals/build/building/multi-stage.md)
|
||||
|
||||
## Next steps
|
||||
|
||||
|
|
|
|||
|
|
@ -27,7 +27,7 @@ Create a GitHub repository, configure the Docker Hub credentials, and push your
|
|||
|
||||
3. Create a new **Repository variable** named `DOCKER_USERNAME` and your Docker ID as value.
|
||||
|
||||
4. Create a new [Personal Access Token (PAT)](../../security/for-developers/access-tokens.md/#create-an-access-token) for Docker Hub. You can name this token `docker-tutorial`. Make sure access permissions include Read and Write.
|
||||
4. Create a new [Personal Access Token (PAT)](/manuals/security/for-developers/access-tokens.md#create-an-access-token) for Docker Hub. You can name this token `docker-tutorial`. Make sure access permissions include Read and Write.
|
||||
|
||||
5. Add the PAT as a **Repository secret** in your GitHub repository, with the name
|
||||
`DOCKERHUB_TOKEN`.
|
||||
|
|
@ -119,7 +119,7 @@ Save the workflow file and run the job.
|
|||
In this section, you learned how to set up a GitHub Actions workflow for your R application.
|
||||
|
||||
Related information:
|
||||
- [Introduction to GitHub Actions](../../build/ci/github-actions/_index.md)
|
||||
- [Introduction to GitHub Actions](/manuals/build/ci/github-actions/_index.md)
|
||||
- [Workflow syntax for GitHub Actions](https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions)
|
||||
|
||||
## Next steps
|
||||
|
|
|
|||
|
|
@ -86,7 +86,7 @@ In this section, you learned how you can containerize and run your R
|
|||
application using Docker.
|
||||
|
||||
Related information:
|
||||
- [Docker Compose overview](../../compose/_index.md)
|
||||
- [Docker Compose overview](/manuals/compose/_index.md)
|
||||
|
||||
## Next steps
|
||||
|
||||
|
|
|
|||
|
|
@ -137,5 +137,5 @@ In this section, you learned how to use Docker Desktop to deploy your applicatio
|
|||
|
||||
Related information:
|
||||
- [Kubernetes documentation](https://kubernetes.io/docs/home/)
|
||||
- [Deploy on Kubernetes with Docker Desktop](../../desktop/kubernetes.md)
|
||||
- [Swarm mode overview](../../engine/swarm/_index.md)
|
||||
- [Deploy on Kubernetes with Docker Desktop](/manuals/desktop/kubernetes.md)
|
||||
- [Swarm mode overview](/manuals/engine/swarm/_index.md)
|
||||
|
|
|
|||
|
|
@ -143,7 +143,7 @@ Press `ctrl+c` in the terminal to stop your application.
|
|||
|
||||
Use Compose Watch to automatically update your running Compose services as you
|
||||
edit and save your code. For more details about Compose Watch, see [Use Compose
|
||||
Watch](../../compose/file-watch.md).
|
||||
Watch](/manuals/compose/file-watch.md).
|
||||
|
||||
Lines 15 to 18 in the `compose.yaml` file contain properties that trigger Docker
|
||||
to rebuild the image when a file in the current working directory is changed:
|
||||
|
|
@ -209,8 +209,8 @@ database and persist data. You also learned how to use Compose Watch to automati
|
|||
|
||||
Related information:
|
||||
- [Compose file reference](/reference/compose-file/)
|
||||
- [Compose file watch](../../compose/file-watch.md)
|
||||
- [Multi-stage builds](../../build/building/multi-stage.md)
|
||||
- [Compose file watch](/manuals/compose/file-watch.md)
|
||||
- [Multi-stage builds](/manuals/build/building/multi-stage.md)
|
||||
|
||||
## Next steps
|
||||
|
||||
|
|
|
|||
|
|
@ -27,7 +27,7 @@ Create a GitHub repository, configure the Docker Hub credentials, and push your
|
|||
|
||||
3. Create a new **Repository variable** named `DOCKER_USERNAME` and your Docker ID as value.
|
||||
|
||||
4. Create a new [Personal Access Token (PAT)](../../security/for-developers/access-tokens.md/#create-an-access-token) for Docker Hub. You can name this token `docker-tutorial`. Make sure access permissions include Read and Write.
|
||||
4. Create a new [Personal Access Token (PAT)](/manuals/security/for-developers/access-tokens.md#create-an-access-token) for Docker Hub. You can name this token `docker-tutorial`. Make sure access permissions include Read and Write.
|
||||
|
||||
5. Add the PAT as a **Repository secret** in your GitHub repository, with the name
|
||||
`DOCKERHUB_TOKEN`.
|
||||
|
|
@ -119,7 +119,7 @@ Save the workflow file and run the job.
|
|||
In this section, you learned how to set up a GitHub Actions workflow for your Ruby on Rails application.
|
||||
|
||||
Related information:
|
||||
- [Introduction to GitHub Actions](../../build/ci/github-actions/_index.md)
|
||||
- [Introduction to GitHub Actions](/manuals/build/ci/github-actions/_index.md)
|
||||
- [Workflow syntax for GitHub Actions](https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions)
|
||||
|
||||
## Next steps
|
||||
|
|
|
|||
|
|
@ -385,7 +385,7 @@ In this section, you learned how you can containerize and run your Ruby
|
|||
application using Docker.
|
||||
|
||||
Related information:
|
||||
- [Docker Compose overview](../../compose/_index.md)
|
||||
- [Docker Compose overview](/manuals/compose/_index.md)
|
||||
|
||||
## Next steps
|
||||
|
||||
|
|
|
|||
|
|
@ -158,5 +158,5 @@ In this section, you learned how to use Docker Desktop to deploy your applicatio
|
|||
|
||||
Related information:
|
||||
- [Kubernetes documentation](https://kubernetes.io/docs/home/)
|
||||
- [Deploy on Kubernetes with Docker Desktop](../../desktop/kubernetes.md)
|
||||
- [Swarm mode overview](../../engine/swarm/_index.md)
|
||||
- [Deploy on Kubernetes with Docker Desktop](/manuals/desktop/kubernetes.md)
|
||||
- [Swarm mode overview](/manuals/engine/swarm/_index.md)
|
||||
|
|
|
|||
|
|
@ -125,7 +125,7 @@ Press `ctrl+c` in the terminal to stop your application and run `docker compose
|
|||
|
||||
Use Compose Watch to automatically update your running Compose services as you
|
||||
edit and save your code. For more details about Compose Watch, see [Use Compose
|
||||
Watch](../../compose/file-watch.md).
|
||||
Watch](/manuals/compose/file-watch.md).
|
||||
|
||||
Open your `compose.yaml` file in an IDE or text editor and then add the Compose
|
||||
Watch instructions. The following is the updated `compose.yaml` file.
|
||||
|
|
@ -189,8 +189,8 @@ database and persist data. You also learned how to use Compose Watch to automati
|
|||
|
||||
Related information:
|
||||
- [Compose file reference](/reference/compose-file/)
|
||||
- [Compose file watch](../../compose/file-watch.md)
|
||||
- [Multi-stage builds](../../build/building/multi-stage.md)
|
||||
- [Compose file watch](/manuals/compose/file-watch.md)
|
||||
- [Multi-stage builds](/manuals/build/building/multi-stage.md)
|
||||
|
||||
## Next steps
|
||||
|
||||
|
|
|
|||
|
|
@ -110,7 +110,7 @@ You should see output like the following.
|
|||
|
||||
## View local images
|
||||
|
||||
To see a list of images you have on your local machine, you have two options. One is to use the Docker CLI and the other is to use [Docker Desktop](../../desktop/use-desktop/images.md). As you are working in the terminal already, take a look at listing images using the CLI.
|
||||
To see a list of images you have on your local machine, you have two options. One is to use the Docker CLI and the other is to use [Docker Desktop](/manuals/desktop/use-desktop/images.md). As you are working in the terminal already, take a look at listing images using the CLI.
|
||||
|
||||
To list images, run the `docker images` command.
|
||||
|
||||
|
|
|
|||
|
|
@ -27,7 +27,7 @@ Create a GitHub repository, configure the Docker Hub credentials, and push your
|
|||
|
||||
3. Create a new **Repository variable** named `DOCKER_USERNAME` and your Docker ID as value.
|
||||
|
||||
4. Create a new [Personal Access Token (PAT)](../../security/for-developers/access-tokens.md/#create-an-access-token) for Docker Hub. You can name this token `docker-tutorial`. Make sure access permissions include Read and Write.
|
||||
4. Create a new [Personal Access Token (PAT)](/manuals/security/for-developers/access-tokens.md#create-an-access-token) for Docker Hub. You can name this token `docker-tutorial`. Make sure access permissions include Read and Write.
|
||||
|
||||
5. Add the PAT as a **Repository secret** in your GitHub repository, with the name
|
||||
`DOCKERHUB_TOKEN`.
|
||||
|
|
@ -118,7 +118,7 @@ Save the workflow file and run the job.
|
|||
In this section, you learned how to set up a GitHub Actions workflow for your Rust application.
|
||||
|
||||
Related information:
|
||||
- [Introduction to GitHub Actions](../../build/ci/github-actions/_index.md)
|
||||
- [Introduction to GitHub Actions](/manuals/build/ci/github-actions/_index.md)
|
||||
- [Workflow syntax for GitHub Actions](https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions)
|
||||
|
||||
## Next steps
|
||||
|
|
|
|||
|
|
@ -223,5 +223,5 @@ In this section, you learned how to use Docker Desktop to deploy your applicatio
|
|||
|
||||
Related information:
|
||||
- [Kubernetes documentation](https://kubernetes.io/docs/home/)
|
||||
- [Deploy on Kubernetes with Docker Desktop](../../desktop/kubernetes.md)
|
||||
- [Swarm mode overview](../../engine/swarm/_index.md)
|
||||
- [Deploy on Kubernetes with Docker Desktop](/manuals/desktop/kubernetes.md)
|
||||
- [Swarm mode overview](/manuals/engine/swarm/_index.md)
|
||||
|
|
|
|||
|
|
@ -7,7 +7,7 @@ description: Learn how to develop your Rust application locally.
|
|||
## Prerequisites
|
||||
|
||||
* You have installed the latest version of [Docker Desktop](/get-started/get-docker.md).
|
||||
* You have completed the walkthroughs in the Docker Desktop [Learning Center](../../desktop/get-started.md) to learn about Docker concepts.
|
||||
* You have completed the walkthroughs in the Docker Desktop [Learning Center](/manuals/desktop/get-started.md) to learn about Docker concepts.
|
||||
* You have a [git client](https://git-scm.com/downloads). The examples in this section use a command-line based git client, but you can use any client.
|
||||
|
||||
## Overview
|
||||
|
|
@ -35,7 +35,7 @@ $ docker network create postgresnet
|
|||
```
|
||||
|
||||
Now you can run PostgreSQL in a container and attach to the volume and network that you created previously. Docker pulls the image from Hub and runs it for you locally.
|
||||
In the following command, option `--mount` is for starting the container with a volume. For more information, see [Docker volumes](/engine/storage/volumes.md).
|
||||
In the following command, option `--mount` is for starting the container with a volume. For more information, see [Docker volumes](/manuals/engine/storage/volumes.md).
|
||||
|
||||
```console
|
||||
$ docker run --rm -d --mount \
|
||||
|
|
@ -277,7 +277,7 @@ secrets:
|
|||
file: db/password.txt
|
||||
```
|
||||
|
||||
Note that the file doesn't specify a network for those 2 services. When you use Compose, it automatically creates a network and connects the services to it. For more information see [Networking in Compose](../../compose/networking.md).
|
||||
Note that the file doesn't specify a network for those 2 services. When you use Compose, it automatically creates a network and connects the services to it. For more information see [Networking in Compose](/manuals/compose/networking.md).
|
||||
|
||||
Before you run the application using Compose, notice that this Compose file specifies a `password.txt` file to hold the database's password. You must create this file as it's not included in the source repository.
|
||||
|
||||
|
|
@ -287,7 +287,7 @@ In the cloned repository's directory, create a new directory named `db` and insi
|
|||
mysecretpassword
|
||||
```
|
||||
|
||||
If you have any other containers running from the previous sections, [stop](./run-containers.md/#stop-start-and-name-containers) them now.
|
||||
If you have any other containers running from the previous sections, [stop](./run-containers.md#stop-start-and-name-containers) them now.
|
||||
|
||||
Now, run the following `docker compose up` command to start your application.
|
||||
|
||||
|
|
@ -314,8 +314,8 @@ You should receive the following response:
|
|||
In this section, you took a look at setting up your Compose file to run your Rust application and database with a single command.
|
||||
|
||||
Related information:
|
||||
- [Docker volumes](/engine/storage/volumes.md)
|
||||
- [Compose overview](../../compose/index.md)
|
||||
- [Docker volumes](/manuals/engine/storage/volumes.md)
|
||||
- [Compose overview](/manuals/compose/index.md)
|
||||
|
||||
## Next steps
|
||||
|
||||
|
|
|
|||
|
|
@ -2,6 +2,11 @@
|
|||
title: Manuals
|
||||
description: Learn how to install, set up, configure, and use Docker products with this collection of user guides
|
||||
keywords: docker, docs, manuals, products, user guides, how-to
|
||||
# hard-code the URL of this page
|
||||
url: /manuals/
|
||||
# remove the /manuals/ prefix for pages in this section
|
||||
cascade:
|
||||
- url: /:sections[1:]/:slugorfilename
|
||||
notoc: true
|
||||
development:
|
||||
- title: Docker Desktop
|
||||
|
|
@ -64,7 +64,7 @@ Your Docker ID becomes your username for hosted Docker services, and [Docker for
|
|||
|
||||
Once you register and verify your Docker ID email address, you can sign in to [your Docker account](https://login.docker.com/u/login/). You can sign in with your email address (or username) and password. Or, you can sign in with your social provider. See [Sign in with your social provider](#sign-in-with-your-social-provider).
|
||||
|
||||
You can also sign in through the CLI using the `docker login` command. For more information, see [`docker login`](../reference/cli/docker/login.md).
|
||||
You can also sign in through the CLI using the `docker login` command. For more information, see [`docker login`](/reference/cli/docker/login.md).
|
||||
|
||||
> [!WARNING]
|
||||
>
|
||||
|
|
@ -0,0 +1,5 @@
|
|||
---
|
||||
build:
|
||||
render: never
|
||||
title: Account and admin FAQ
|
||||
---
|
||||
|
|
@ -51,7 +51,7 @@ A company name must be unique to that of its child organization. If a child orga
|
|||
|
||||
### How does a company owner add an organization to the company?
|
||||
|
||||
You can add organizations to a company in the [Admin Console](../../admin/company/organizations.md/#add-organizations-to-a-company.md) or [Docker Hub](../../admin/company/new-company.md/#add-organizations-to-a-company.md).
|
||||
You can add organizations to a company in the [Admin Console](../../admin/company/organizations.md#add-organizations-to-a-company.md) or [Docker Hub](../../admin/company/new-company.md#add-organizations-to-a-company.md).
|
||||
|
||||
### How does a company owner manage SSO/SCIM settings from a company?
|
||||
|
||||
|
|
@ -28,7 +28,7 @@ No. Organization owners can invite users with their email address, and also assi
|
|||
|
||||
Yes. You can [enforce sign-in](../../security/for-admins/enforce-sign-in/_index.md) and some benefits are:
|
||||
|
||||
- Administrators can enforce features like [Image Access Management](/security/for-admins/hardened-desktop/image-access-management.md) and [Registry Access Management](../../security/for-admins/hardened-desktop/registry-access-management.md).
|
||||
- Administrators can enforce features like [Image Access Management](/manuals/security/for-admins/hardened-desktop/image-access-management.md) and [Registry Access Management](../../security/for-admins/hardened-desktop/registry-access-management.md).
|
||||
- Administrators can ensure compliance by blocking Docker Desktop usage for users who don't sign in as members of the organization.
|
||||
|
||||
### If a user has their personal email associated with a user account in Docker Hub, do they have to convert to using the organization's domain before they can be invited to join an organization?
|
||||
|
Before Width: | Height: | Size: 64 KiB After Width: | Height: | Size: 64 KiB |
|
Before Width: | Height: | Size: 26 KiB After Width: | Height: | Size: 26 KiB |
|
Before Width: | Height: | Size: 17 KiB After Width: | Height: | Size: 17 KiB |
|
Before Width: | Height: | Size: 20 KiB After Width: | Height: | Size: 20 KiB |
|
|
@ -19,7 +19,7 @@ Owners can also see the activity logs for their repository if the repository is
|
|||
|
||||
> [!NOTE]
|
||||
>
|
||||
> Activity logs requires a [Docker Team or Business subscription](../../../subscription/_index.md).
|
||||
> Activity logs requires a [Docker Team or Business subscription](/manuals/subscription/_index.md).
|
||||
|
||||
## Manage activity logs
|
||||
|
||||
|
|
@ -99,7 +99,7 @@ configure your organization.
|
|||
- **Settings**: Displays information about your
|
||||
organization, and allows you to view and change your repository privacy
|
||||
settings, configure org permissions such as
|
||||
[Image Access Management](/security/for-admins/hardened-desktop/image-access-management.md), configure notification settings, and [deactivate](../deactivate-account.md#deactivate-an-organization) You can also update your organization name and company name that appear on your organization landing page. You must be an owner to access the
|
||||
[Image Access Management](/manuals/security/for-admins/hardened-desktop/image-access-management.md), configure notification settings, and [deactivate](../deactivate-account.md#deactivate-an-organization) You can also update your organization name and company name that appear on your organization landing page. You must be an owner to access the
|
||||
organization's **Settings** page.
|
||||
|
||||
- **Billing**: Displays information about your existing
|
||||
|
|
@ -0,0 +1,5 @@
|
|||
---
|
||||
build:
|
||||
render: never
|
||||
title: Docker Core billing
|
||||
---
|
||||
|
|
@ -16,7 +16,7 @@ In this section, learn how to get started with a Docker Core subscription for in
|
|||
2. Select your avatar in the top-right corner then select **Billing**.
|
||||
3. In **Billing Details**, select your personal account.
|
||||
4. Select **Buy now**.
|
||||
5. To continue to use [**Docker Core Personal**](/subscription/core-subscription/details/#docker-personal), select **Continue with Personal**. To buy [**Docker Core Pro**](/subscription/core-subscription/details/#docker-pro), select **Buy Now** on the **Pro** card.
|
||||
5. To continue to use [**Docker Core Personal**](/manuals/subscription/core-subscription/details.md#docker-personal), select **Continue with Personal**. To buy [**Docker Core Pro**](/manuals/subscription/core-subscription/details.md#docker-pro), select **Buy Now** on the **Pro** card.
|
||||
6. Enter your billing information, then select **Submit**.
|
||||
7. Follow the on-screen instructions to confirm monthly or annual billing cycle and enter your payment information.
|
||||
8. Select **Subscribe**.
|
||||
|
|
@ -64,6 +64,6 @@ Once you've signed up and created a builder, continue by
|
|||
[setting up the builder in your local environment](./setup.md).
|
||||
|
||||
For more information about the available subscription plans, see
|
||||
[Docker Build Cloud subscriptions and features](/subscription/build-cloud/build-details.md).
|
||||
[Docker Build Cloud subscriptions and features](/manuals/subscription/build-cloud/build-details.md).
|
||||
For information about roles and permissions related to Docker Build Cloud, see
|
||||
[Roles and Permissions](/security/for-admins/roles-and-permissions.md#docker-build-cloud).
|
||||
[Roles and Permissions](/manuals/security/for-admins/roles-and-permissions.md#docker-build-cloud).
|
||||
|
|
@ -37,7 +37,7 @@ See [Loading build results](./usage/#loading-build-results) for details.
|
|||
>
|
||||
> Version 4.0.0 and later of `docker/build-push-action` and
|
||||
> `docker/bake-action` builds images with [provenance attestations by
|
||||
> default](/build/ci/github-actions/attestations.md#default-provenance). Docker
|
||||
> default](/manuals/build/ci/github-actions/attestations.md#default-provenance). Docker
|
||||
> Build Cloud automatically attempts to load images to the local image store if
|
||||
> you don't explicitly push them to a registry.
|
||||
>
|
||||
|
|
@ -30,11 +30,11 @@ more efficient:
|
|||
- [Multi-threaded tools](#multi-threaded-tools)
|
||||
|
||||
For more information on how to optimize your builds, see
|
||||
[Building best practices](/build/building/best-practices.md).
|
||||
[Building best practices](/manuals/build/building/best-practices.md).
|
||||
|
||||
### Dockerignore files
|
||||
|
||||
Using a [`.dockerignore` file](/build/concepts/context.md#dockerignore-files),
|
||||
Using a [`.dockerignore` file](/manuals/build/concepts/context.md#dockerignore-files),
|
||||
you can be explicit about which local files you don’t want to include in the
|
||||
build context. Files caught by the glob patterns you specify in your
|
||||
ignore-file aren't transferred to the remote builder.
|
||||
Some files were not shown because too many files have changed in this diff Show More
Loading…
Reference in New Issue