diff options
Diffstat (limited to 'doc/administration/packages/container_registry.md')
| -rw-r--r-- | doc/administration/packages/container_registry.md | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/doc/administration/packages/container_registry.md b/doc/administration/packages/container_registry.md index a6829b90f18..74483b65c4d 100644 --- a/doc/administration/packages/container_registry.md +++ b/doc/administration/packages/container_registry.md @@ -1025,15 +1025,15 @@ You may want to add the `-m` flag to [remove untagged manifests and unreferenced Before diving in to the following sections, here's some basic troubleshooting: 1. Check to make sure that the system clock on your Docker client and GitLab server have - been synchronized (e.g. via NTP). + been synchronized (for example, via NTP). 1. If you are using an S3-backed Registry, double check that the IAM permissions and the S3 credentials (including region) are correct. See [the sample IAM policy](https://docs.docker.com/registry/storage-drivers/s3/) for more details. -1. Check the Registry logs (e.g. `/var/log/gitlab/registry/current`) and the GitLab production logs - for errors (e.g. `/var/log/gitlab/gitlab-rails/production.log`). You may be able to find clues +1. Check the Registry logs (for example `/var/log/gitlab/registry/current`) and the GitLab production logs + for errors (for example `/var/log/gitlab/gitlab-rails/production.log`). You may be able to find clues there. ### Using self-signed certificates with Container Registry @@ -1359,7 +1359,7 @@ For Omnibus installations: [image upgrade](#images-upgrade)) steps. You should [stop](https://docs.gitlab.com/omnibus/maintenance/#starting-and-stopping) the registry service before replacing its binary and start it right after. No registry configuration changes are required. - + #### Source installations For source installations, locate your `registry` binary and temporarily replace it with the one @@ -1461,7 +1461,7 @@ no errors are generated by the curl commands. #### Running the Docker daemon with a proxy For Docker to connect through a proxy, you must start the Docker daemon with the -proper environment variables. The easiest way is to shutdown Docker (e.g. `sudo initctl stop docker`) +proper environment variables. The easiest way is to shutdown Docker (for example `sudo initctl stop docker`) and then run Docker by hand. As root, run: ```shell |