Troubleshooting

Verify that Docker is working correctly
The following command, if it runs successfully, will verify that docker is running correctly.
1
$ docker run hello-world
2
Unable to find image 'hello-world:latest' locally
3
latest: Pulling from library/hello-world
4
0e03bdcc26d7: Pull complete 
5
Digest: sha256:8e3114318a995a1ee497790535e7b88365222a21771ae7e53687ad76563e8e76
6
Status: Downloaded newer image for hello-world:latest
7
​
8
Hello from Docker!
9
This message shows that your installation appears to be working correctly.
10
​
11
To generate this message, Docker took the following steps:
12
 1. The Docker client contacted the Docker daemon.
13
 2. The Docker daemon pulled the "hello-world" image from the Docker Hub.
14
    (amd64)
15
 3. The Docker daemon created a new container from that image which runs the
16
    executable that produces the output you are currently reading.
17
 4. The Docker daemon streamed that output to the Docker client, which sent it
18
    to your terminal.
19
​
20
To try something more ambitious, you can run an Ubuntu container with:
21
 $ docker run -it ubuntu bash
22
​
23
Share images, automate workflows, and more with a free Docker ID:
24
 https://hub.docker.com/
25
​
26
For more examples and ideas, visit:
27
 https://docs.docker.com/get-started/
Copied!
Docker error messages
message
cause
fix
engine build error: docker build failed: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
Docker daemon is not running.
Restart the Docker daemon
read tcp xxx.xxx.xxx.xxx:443 i/o timeout
Cannot connect to remote repository
This is a frequent and probably transient error. Try again.
Troubleshooting
Test plans fail to finish before context expires
This may be caused by high load on the host machine. Try to reduce the load using the following:
Reduce the number of instances
terminate old test plan containers (if any) with testground terminate
close applications which may cause enough load to interfere with the test
Test plans fail while waiting on a barrier
This may indicate a problem with the sync service or the sidecar. Investigate and try again.
docker logs testground-redis
docker kill testground-redis
Testground containers are killed before plans finished.
It's possible that the the system is killed after running out of memory or that another system problem is occurring.
docker events
docker logs <suspicious_container>
docker stats
Healthchecks
Testground comes equipped with healthchecks that have some self-fixing features. These healthchecks are able to fix any container that is added by Testground, but it cannot fix anything related to your user account or host system.
To view current healthcheck status, and issue automatic remediation, use the following commands. Under normal circumstances, this is unnecessary since they will be started automatically if a problem is detected.
1
# view the healthcheck status
2
$ testground healthcheck --runner local:docker
3
​
4
finished checking runner local:docker
5
Checks:
6
- local-outputs-dir: ok; directory exists.
7
- control-network: failed; network does not exist.
8
- local-grafana: failed; container not found.
9
- local-redis: failed; container not found.
10
- local-influxdb: failed; container not found.
11
- sidecar-container: failed; container not found.
12
Fixes:
13
- control-network: omitted; 
14
- local-grafana: omitted; 
15
- local-redis: omitted; 
16
- local-influxdb: omitted; 
17
- sidecar-container: omitted; 
18
​
19
​
20
# fix the problems automatically
21
$ testground healthcheck --runner local:docker --fix
22
​
23
... a few seconds later
24
​
25
finished checking runner local:docker
26
Checks:
27
- local-outputs-dir: ok; directory exists.
28
- control-network: failed; network does not exist.
29
- local-grafana: failed; container not found.
30
- local-redis: failed; container not found.
31
- local-influxdb: failed; container not found.
32
- sidecar-container: failed; container not found.
33
Fixes:
34
- local-outputs-dir: unnecessary; 
35
- control-network: ok; network created.
36
- local-grafana: ok; container started
37
- local-redis: ok; container started
38
- local-influxdb: ok; container started
39
- sidecar-container: ok; container started
Copied!

Runner flags

Next - Runner library

cluster:k8s

Last modified 1yr ago

Copy link

Contents

Verify that Docker is working correctly

Docker error messages

Troubleshooting

Healthchecks