mirror of https://github.com/docker/docs.git
language/golang: fix some broken links
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
This commit is contained in:
parent
08daa0e7ed
commit
7e9fdf93fe
|
@ -11,7 +11,7 @@ redirect_from:
|
|||
## Prerequisites
|
||||
|
||||
* Some understanding of Go and its toolchain. This is not a tutorial on Go. If you are new to the language, the [Go website](https://golang.org/){: target="_blank" rel="noopener" class="_"} is a good starting point, so go (pun intended) check it out.
|
||||
* Some awareness of basic Docker concepts. If unsure, work through the orientation and setup in Get started [Part 1](/get-started/).
|
||||
* Some awareness of basic Docker concepts. If unsure, work through the orientation and setup in Get started [Part 1](../../get-started/index.md).
|
||||
|
||||
## Overview
|
||||
|
||||
|
@ -267,7 +267,7 @@ Your exact output will vary, but provided there aren't any errors, you should se
|
|||
|
||||
## View local images
|
||||
|
||||
To see the list of images we have on our local machine, we have two options. One is to use the CLI and the other is to use [Docker Desktop](/products/docker-desktop). Since we are currently working in the terminal, let’s take a look at listing images with the CLI.
|
||||
To see the list of images we have on our local machine, we have two options. One is to use the CLI and the other is to use [Docker Desktop](../../desktop/index.md). Since we are currently working in the terminal, let’s take a look at listing images with the CLI.
|
||||
|
||||
To list images, simply run the `images` command:
|
||||
|
||||
|
@ -393,7 +393,7 @@ docker-gs-ping latest 336a3f164d0f About an hour ago 540MB
|
|||
|
||||
This is due to the fact that the ["distroless" base image](https://github.com/GoogleContainerTools/distroless) that we have used to deploy our Go application is very barebones and is meant for lean deployments of static binaries.
|
||||
|
||||
For more information on multi-stage builds, please feel free to check out [other parts](/develop/develop-images/multistage-build/) of Docker documentation. This is, however, not essential for our progress here, so we'll leave it at that.
|
||||
For more information on multi-stage builds, please feel free to check out [other parts](../../develop/develop-images/multistage-build.md) of Docker documentation. This is, however, not essential for our progress here, so we'll leave it at that.
|
||||
|
||||
## Next steps
|
||||
|
||||
|
|
|
@ -67,7 +67,7 @@ daed20bbecce host host local
|
|||
6aee44f40a39 none null local
|
||||
```
|
||||
|
||||
Our 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 is not relevant to our current discussion, you can learn more about Docker networking in the [networking overview](../../network/) section.
|
||||
Our 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 is not relevant to our current discussion, you can learn more about Docker networking in the [networking overview](../../network/index.md) section.
|
||||
|
||||
### Choose good names for volumes and networks
|
||||
|
||||
|
@ -717,7 +717,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 the following part of Docker documentation: [Manage data in Docker](../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 the following part of Docker documentation: [Manage data in Docker](../../storage/index.md).
|
||||
|
||||
### CockroachDB clusters
|
||||
|
||||
|
@ -728,7 +728,7 @@ Such distributed set-up offers interesting possibilities, such as applying _Chao
|
|||
If you are interested in experimenting with CockroachDB clusters, check out:
|
||||
|
||||
* [Start a CockroachDB Cluster in Docker](https://www.cockroachlabs.com/docs/v20.2/start-a-local-cluster-in-docker-mac.html) article; and
|
||||
* Documentation for Docker Compose keywords [`deploy`](../../compose/compose-file/compose-file-v3/#deploy) and [`replicas`](../../compose/compose-file/compose-file-v3/#replicas).
|
||||
* Documentation for Docker Compose keywords [`deploy`](../../compose/compose-file/compose-file-v3.md#deploy) and [`replicas`](../../compose/compose-file/compose-file-v3.md#replicas).
|
||||
|
||||
### Other databases
|
||||
|
||||
|
@ -744,6 +744,6 @@ In the next module, we’ll take a look at one possible approach to running func
|
|||
|
||||
## Feedback
|
||||
|
||||
Help us improve this topic by providing your feedback. Let us know what you think by creating an issue in the [Docker Docs ](https://github.com/docker/docker.github.io/issues/new?title=[Golang%20docs%20feedback]){:target="_blank" rel="noopener" class="_"} GitHub repository. Alternatively, [create a PR](https://github.com/docker/docker.github.io/pulls){:target="_blank" rel="noopener" class="_"} to suggest updates.
|
||||
Help us improve this topic by providing your feedback. Let us know what you think by creating an issue in the [Docker Docs](https://github.com/docker/docker.github.io/issues/new?title=[Golang%20docs%20feedback]){:target="_blank" rel="noopener" class="_"} GitHub repository. Alternatively, [create a PR](https://github.com/docker/docker.github.io/pulls){:target="_blank" rel="noopener" class="_"} to suggest updates.
|
||||
|
||||
<br />
|
||||
|
|
Loading…
Reference in New Issue