docker
/
docs
mirror of https://github.com/docker/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #17502 from craig-osterhout/update-go-guide-repos 

Update go guide repos
This commit is contained in:
Craig Osterhout 2023-06-21 09:47:30 -07:00 committed by GitHub
parent 9fc3e39c0d 194131d3ed
commit 4d153638cc
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
language/golang/build-images.md
View File

@ -39,12 +39,12 @@ The application listens on a TCP port defined by the value of environment variab
The application is *stateless*.
The complete source code for the application is on GitHub: [github.com/olliefr/docker-gs-ping](https://github.com/olliefr/docker-gs-ping){: target="_blank" rel="noopener" class="_"}. You are encouraged to fork it and experiment with it as much as you like.
The complete source code for the application is on GitHub: [github.com/docker/docker-gs-ping](https://github.com/docker/docker-gs-ping){: target="_blank" rel="noopener" class="_"}. You are encouraged to fork it and experiment with it as much as you like.
To continue, we clone the application repository to our local machine:
```console
$ git clone https://github.com/olliefr/docker-gs-ping
$ git clone https://github.com/docker/docker-gs-ping
```
The application's `main.go` file is fairly straightforward, if you are familiar with Go:

4
language/golang/develop.md
View File

@ -171,12 +171,12 @@ Now that we have started and configured the database engine, we can switch our a
The example application for this module is an extended version of `docker-gs-ping` application we've used in the previous modules. You have two options:
* You can update your local copy of `docker-gs-ping` to match the new extended version presented in this chapter; or
* You can clone the [olliefr/docker-gs-ping-roach](https://github.com/olliefr/docker-gs-ping-roach) repo. This latter approach is recommended.
* You can clone the [docker/docker-gs-ping-roach](https://github.com/docker/docker-gs-ping-roach) repo. This latter approach is recommended.
To checkout the example application, run:
```console
$ git clone https://github.com/olliefr/docker-gs-ping-roach.git
$ git clone https://github.com/docker/docker-gs-ping-roach.git
# ... output omitted ...
```

6
language/golang/run-tests.md
View File

@ -57,7 +57,7 @@ As you can see, this is a high-level test, unconcerned with the implementation d
* the test is using [`ory/dockertest`](https://github.com/ory/dockertest) Go module;
* the test assumes that the Docker engine instance is running on the same machine where the test is being run.
The second test in `main_test.go` has almost identical structure but it tests _another_ business requirement of our application. You are welcome to have a look at all available tests in [`docker-gs-ping/main_test.go`](https://github.com/olliefr/docker-gs-ping/blob/main/main_test.go).
The second test in `main_test.go` has almost identical structure but it tests _another_ business requirement of our application. You are welcome to have a look at all available tests in [`docker-gs-ping/main_test.go`](https://github.com/docker/docker-gs-ping/blob/main/main_test.go).
## Run tests locally
@ -77,7 +77,7 @@ Now that the Docker image for our application had been built, we can run the tes
```console
$ go test ./...
ok github.com/olliefr/docker-gs-ping 2.564s
ok github.com/docker/docker-gs-ping 2.564s
```
That was a bit... underwhelming? Let's ask it to print a bit more detail, just to be sure:
@ -91,7 +91,7 @@ $ go test -v ./...
main_test.go:83: container not ready, waiting...
--- PASS: TestHealthCheck (1.40s)
PASS
ok github.com/olliefr/docker-gs-ping 6.670s
ok github.com/docker/docker-gs-ping 6.670s
```
So, the tests do, indeed, pass. Note, how retrying using exponential back-off helped avoiding failing tests while the containers are being initialised. What happens in each test is that `ory/dockertest` module connects to the local Docker engine instance and instructs it to spin up a container using the image, identified by the tag `docker-gs-ping:latest`. Starting up a container may take a while, so our tests retry accessing the container until the container is ready to respond to requests.