diff options
| author | Stan Hu <stanhu@gmail.com> | 2016-08-02 15:24:15 -0700 |
|---|---|---|
| committer | Stan Hu <stanhu@gmail.com> | 2016-08-02 15:24:15 -0700 |
| commit | 2c9cce0feb8bd4e10f3406493eff30e783782d15 (patch) | |
| tree | 6857c996f3f3dc63b3bc0a2dad76c83ecad03272 | |
| parent | 46385e4e5a88a4ac614f680094b9226778cee64a (diff) | |
| download | gitlab-ce-add-docker-debugging-docs.tar.gz | |
Grammar improvementsadd-docker-debugging-docs
[ci skip]
| -rw-r--r-- | doc/container_registry/troubleshooting.md | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/container_registry/troubleshooting.md b/doc/container_registry/troubleshooting.md index c24c80518dd..8008bf29935 100644 --- a/doc/container_registry/troubleshooting.md +++ b/doc/container_registry/troubleshooting.md @@ -43,10 +43,10 @@ a08f14ef632e: Pushing [==================================================>] 2.04 error parsing HTTP 403 response body: unexpected end of JSON input: "" ``` -This error is ambiguous, as it's not clear whether the 403 is coming from the GitLab Rails -application, the Docker registry, or something else. In this case, we know that since -the login succeeded, we probably need to look at the communication between the client -and the registry. +This error is ambiguous, as it's not clear whether the 403 is coming from the +GitLab Rails application, the Docker registry, or something else. In this +case, since we know that since the login succeeded, we probably need to look +at the communication between the client and the registry. The REST API between the Docker client and registry is [described here](https://docs.docker.com/registry/spec/api/). Normally, one would just |