clearlinux/docker
2
0
Fork 0
mirror of https://github.com/clearlinux/docker.git synced 2026-09-04 12:41:42 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #7363 from lcoote/master

Browse Source 
#1852 Remote API documentation incorrect regarding private registries
This commit is contained in:
Sven Dowideit
2014-08-03 21:21:43 +10:00
parent bec676e2de a5c5dc121c
commit 41a553ca35
15 changed files with 50 additions and 65 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/sources/reference/api/docker_remote_api_v1.0.md
-6
View File
@@ -677,12 +677,6 @@ Push the image `name` on the registry
{{ STREAM }}
Query Parameters:
 
- **registry** – the registry you wan to push, optional
Status Codes:
- **200** – no error
docs/sources/reference/api/docker_remote_api_v1.1.md
-6
View File
@@ -687,12 +687,6 @@ Push the image `name` on the registry
{"error":"Invalid..."}
...
Query Parameters:
 
- **registry** – the registry you wan to push, optional
Status Codes:
- **200** – no error
docs/sources/reference/api/docker_remote_api_v1.10.md
+10 -1
View File
@@ -853,11 +853,20 @@ Push the image `name` on the registry
{"error":"Invalid..."}
...
If you wish to push an image on to a private registry, that image must already have been tagged
into a repository which references that registry host name and port. This repository name should
then be used in the URL. This mirrors the flow of the CLI.
**Example request**:
POST /images/registry.acme.com:5000/test/push HTTP/1.1
Query Parameters:
 
- **registry** – the registry you wan to push, optional
- **tag** – the tag to associate with the image on the registry, optional
Request Headers:
docs/sources/reference/api/docker_remote_api_v1.11.md
+10 -1
View File
@@ -861,11 +861,20 @@ Push the image `name` on the registry
{"error":"Invalid..."}
...
If you wish to push an image on to a private registry, that image must already have been tagged
into a repository which references that registry host name and port. This repository name should
then be used in the URL. This mirrors the flow of the CLI.
**Example request**:
POST /images/registry.acme.com:5000/test/push HTTP/1.1
Query Parameters:
 
- **registry** – the registry you wan to push, optional
- **tag** – the tag to associate with the image on the registry, optional
Request Headers:
docs/sources/reference/api/docker_remote_api_v1.12.md
+10 -1
View File
@@ -914,11 +914,20 @@ Push the image `name` on the registry
{"error":"Invalid..."}
...
If you wish to push an image on to a private registry, that image must already have been tagged
into a repository which references that registry host name and port. This repository name should
then be used in the URL. This mirrors the flow of the CLI.
**Example request**:
POST /images/registry.acme.com:5000/test/push HTTP/1.1
Query Parameters:
 
- **registry** – the registry you wan to push, optional
- **tag** – the tag to associate with the image on the registry, optional
Request Headers:
docs/sources/reference/api/docker_remote_api_v1.13.md
+10 -1
View File
@@ -914,11 +914,20 @@ Push the image `name` on the registry
{"error":"Invalid..."}
...
If you wish to push an image on to a private registry, that image must already have been tagged
into a repository which references that registry host name and port. This repository name should
then be used in the URL. This mirrors the flow of the CLI.
**Example request**:
POST /images/registry.acme.com:5000/test/push HTTP/1.1
Query Parameters:
 
- **registry** – the registry you wan to push, optional
- **tag** – the tag to associate with the image on the registry, optional
Request Headers:
docs/sources/reference/api/docker_remote_api_v1.14.md
+10 -1
View File
@@ -920,11 +920,20 @@ Push the image `name` on the registry
{"error":"Invalid..."}
...
If you wish to push an image on to a private registry, that image must already have been tagged
into a repository which references that registry host name and port. This repository name should
then be used in the URL. This mirrors the flow of the CLI.
**Example request**:
POST /images/registry.acme.com:5000/test/push HTTP/1.1
Query Parameters:
 
- **registry** – the registry you wan to push, optional
- **tag** – the tag to associate with the image on the registry, optional
Request Headers:
docs/sources/reference/api/docker_remote_api_v1.2.md
-6
View File
@@ -706,12 +706,6 @@ Push the image `name` on the registry
{"error":"Invalid..."}
...
Query Parameters:
 
- **registry** – the registry you wan to push, optional
Status Codes:
- **200** – no error
docs/sources/reference/api/docker_remote_api_v1.3.md
-6
View File
@@ -755,12 +755,6 @@ Push the image `name` on the registry
{"error":"Invalid..."}
...
Query Parameters:
 
- **registry** – the registry you wan to push, optional
Status Codes:
- **200** – no error
docs/sources/reference/api/docker_remote_api_v1.4.md
-6
View File
@@ -801,12 +801,6 @@ Push the image `name` on the registry
{"status":"Pushing..."} {"status":"Pushing", "progress":"1/? (n/a)"}
{"error":"Invalid..."} ...
Query Parameters:
 
- **registry** – the registry you wan to push, optional
Status Codes:
- **200** – no error :statuscode 404: no such image :statuscode
docs/sources/reference/api/docker_remote_api_v1.5.md
-6
View File
@@ -805,12 +805,6 @@ Push the image `name` on the registry
The `X-Registry-Auth` header can be used to
include a base64-encoded AuthConfig object.
Query Parameters:
 
- **registry** – the registry you wan to push, optional
Status Codes:
- **200** – no error
docs/sources/reference/api/docker_remote_api_v1.6.md
-6
View File
@@ -910,12 +910,6 @@ Push the image `name` on the registry
> The `X-Registry-Auth` header can be used to
> include a base64-encoded AuthConfig object.
Query Parameters:
 
- **registry** – the registry you wan to push, optional
Status Codes:
- **200** – no error :statuscode 404: no such image :statuscode
docs/sources/reference/api/docker_remote_api_v1.7.md
-6
View File
@@ -828,12 +828,6 @@ Push the image `name` on the registry
{"error":"Invalid..."}
...
Query Parameters:
 
- **registry** – the registry you wan to push, optional
Request Headers:
 
docs/sources/reference/api/docker_remote_api_v1.8.md
-6
View File
@@ -870,12 +870,6 @@ Push the image `name` on the registry
{"error":"Invalid..."}
...
Query Parameters:
 
- **registry** – the registry you wan to push, optional
Request Headers:
 
docs/sources/reference/api/docker_remote_api_v1.9.md
-6
View File
@@ -874,12 +874,6 @@ Push the image `name` on the registry
{"error":"Invalid..."}
...
Query Parameters:
 
- **registry** – the registry you wan to push, optional
Request Headers: