Skip to content

Commit 86d0d42

Browse files
craig-osterhoutcraig-osterhout
committed
fix tables
Signed-off-by: Craig <[email protected]>
1 parent 3d40861 commit 86d0d42

File tree

1 file changed

+26
-26
lines changed

1 file changed

+26
-26
lines changed

‎content/reference/api/registry/_index.md‎

Lines changed: 26 additions & 26 deletions
Original file line numberDiff line numberDiff line change
@@ -161,9 +161,9 @@ hex := /[A-Fa-f0-9]+/
161161

162162
Some examples of _digests_ include the following:
163163

164-
digest | description |
165-
----------------------------------------------------------------------------------|------------------------------------------------
166-
sha256:6c3c624b58dbbcd3c0dd82b4c53f04194d1247c6eebdaab7c610cf7d66709b3b | Common sha256 based digest |
164+
| digest | description |
165+
|-------------------------------------------------------------------------|----------------------------|
166+
| sha256:6c3c624b58dbbcd3c0dd82b4c53f04194d1247c6eebdaab7c610cf7d66709b3b | Common sha256 based digest |
167167

168168
While the _algorithm_ does let one implement a wide variety of
169169
algorithms, compliant implementations should use sha256. Heavy processing of
@@ -215,12 +215,12 @@ process of pulling an image centers around retrieving these two components.
215215
The first step in pulling an image is to retrieve the manifest. For reference,
216216
the relevant manifest fields for the registry are the following:
217217

218-
field | description |
219-
----------|------------------------------------------------|
220-
name | The name of the image. |
221-
tag | The tag for this version of the image. |
222-
fsLayers | A list of layer descriptors (including digest) |
223-
signature | A JWS used to verify the manifest content |
218+
| field | description |
219+
|-----------|------------------------------------------------|
220+
| name | The name of the image. |
221+
| tag | The tag for this version of the image. |
222+
| fsLayers | A list of layer descriptors (including digest) |
223+
| signature | A JWS used to verify the manifest content |
224224

225225

226226
When the manifest is in hand, the client must verify the signature to ensure
@@ -727,23 +727,23 @@ The detail for each endpoint is covered in the following sections.
727727

728728
The error codes encountered via the API are enumerated in the following table:
729729

730-
|Code|Message|Description|
731-
|----|-------|-----------|
732-
`BLOB_UNKNOWN` | blob unknown to registry | This error may be returned when a blob is unknown to the registry in a specified repository. This can be returned with a standard get or if a manifest references an unknown layer during upload.
733-
`BLOB_UPLOAD_INVALID` | blob upload invalid | The blob upload encountered an error and can no longer proceed.
734-
`BLOB_UPLOAD_UNKNOWN` | blob upload unknown to registry | If a blob upload has been canceled or was never started, this error code may be returned.
735-
`DIGEST_INVALID` | provided digest did not match uploaded content | When a blob is uploaded, the registry will check that the content matches the digest provided by the client. The error may include a detail structure with the key "digest", including the invalid digest string. This error may also be returned when a manifest includes an invalid layer digest.
736-
`MANIFEST_BLOB_UNKNOWN` | blob unknown to registry | This error may be returned when a manifest blob is unknown to the registry.
737-
`MANIFEST_INVALID` | manifest invalid | During upload, manifests undergo several checks ensuring validity. If those checks fail, this error may be returned, unless a more specific error is included. The detail will contain information the failed validation.
738-
`MANIFEST_UNKNOWN` | manifest unknown | This error is returned when the manifest, identified by name and tag is unknown to the repository.
739-
`MANIFEST_UNVERIFIED` | manifest failed signature verification | During manifest upload, if the manifest fails signature verification, this error will be returned.
740-
`NAME_INVALID` | invalid repository name | Invalid repository name encountered either during manifest validation or any API operation.
741-
`NAME_UNKNOWN` | repository name not known to registry | This is returned if the name used during an operation is unknown to the registry.
742-
`SIZE_INVALID` | provided length did not match content length | When a layer is uploaded, the provided size will be checked against the uploaded content. If they do not match, this error will be returned.
743-
`TAG_INVALID` | manifest tag did not match URI | During a manifest upload, if the tag in the manifest does not match the URI tag, this error will be returned.
744-
`UNAUTHORIZED` | authentication required | The access controller was unable to authenticate the client. Often this will be accompanied by a Www-Authenticate HTTP response header indicating how to authenticate.
745-
`DENIED` | requested access to the resource is denied | The access controller denied access for the operation on a resource.
746-
`UNSUPPORTED` | The operation is unsupported. | The operation was unsupported due to a missing implementation or invalid set of parameters.
730+
| Code | Message | Description |
731+
|-------------------------|------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
732+
| `BLOB_UNKNOWN` | blob unknown to registry | This error may be returned when a blob is unknown to the registry in a specified repository. This can be returned with a standard get or if a manifest references an unknown layer during upload. |
733+
| `BLOB_UPLOAD_INVALID` | blob upload invalid | The blob upload encountered an error and can no longer proceed. |
734+
| `BLOB_UPLOAD_UNKNOWN` | blob upload unknown to registry | If a blob upload has been canceled or was never started, this error code may be returned. |
735+
| `DIGEST_INVALID` | provided digest did not match uploaded content | When a blob is uploaded, the registry will check that the content matches the digest provided by the client. The error may include a detail structure with the key "digest", including the invalid digest string. This error may also be returned when a manifest includes an invalid layer digest. |
736+
| `MANIFEST_BLOB_UNKNOWN` | blob unknown to registry | This error may be returned when a manifest blob is unknown to the registry. |
737+
| `MANIFEST_INVALID` | manifest invalid | During upload, manifests undergo several checks ensuring validity. If those checks fail, this error may be returned, unless a more specific error is included. The detail will contain information the failed validation. |
738+
| `MANIFEST_UNKNOWN` | manifest unknown | This error is returned when the manifest, identified by name and tag is unknown to the repository. |
739+
| `MANIFEST_UNVERIFIED` | manifest failed signature verification | During manifest upload, if the manifest fails signature verification, this error will be returned. |
740+
| `NAME_INVALID` | invalid repository name | Invalid repository name encountered either during manifest validation or any API operation. |
741+
| `NAME_UNKNOWN` | repository name not known to registry | This is returned if the name used during an operation is unknown to the registry. |
742+
| `SIZE_INVALID` | provided length did not match content length | When a layer is uploaded, the provided size will be checked against the uploaded content. If they do not match, this error will be returned. |
743+
| `TAG_INVALID` | manifest tag did not match URI | During a manifest upload, if the tag in the manifest does not match the URI tag, this error will be returned.
744+
| `UNAUTHORIZED` | authentication required | The access controller was unable to authenticate the client. Often this will be accompanied by a Www-Authenticate HTTP response header indicating how to authenticate.|
745+
| `DENIED` | requested access to the resource is denied | The access controller denied access for the operation on a resource.|
746+
| `UNSUPPORTED` | The operation is unsupported. | The operation was unsupported due to a missing implementation or invalid set of parameters.|
747747

748748
### Base
749749

0 commit comments

Comments
 (0)