![]() If the object that would otherwise be returned is a manifest list, the Type is not present in an Accept header, the registry will assume that theĬlient cannot handle the manifest as-is, and rewrite it on the fly into the oldįormat. If the manifest being requested uses the new format, and the appropriate media Returned from the endpoint is in the old format, or is an image manifest or UpdatedĬlients should check the Content-Type header to see whether the manifest When pulling images, clients indicate support for this new version of theĪpplication/.v2+json andĪpplication/.list.v2+json media types in anĪccept header when making a request to the manifests endpoint. Presumably because the registry only supports the old format, the client mayįall back to uploading a manifest in the old format. When pushing images, clients which support the new manifest format should firstĬonstruct a manifest in the new format. The registry will continue to accept uploads of manifests in both the old and Listing a required CPU feature (for example sse4 or aes).Įxample showing a simple manifest list pointing to image manifests for two platforms: The optional features field specifies an array of strings, each The optional variant field specifies a variant of the CPU, forĮxample armv6l to specify a particular CPU variant of the ARM CPU. #Manifest definition windowsThe optional os.features field specifies an array of strings,Įach listing a required OS feature (for example on Windows The optional os.version field specifies the operating system version, The os field specifies the operating system, for example The architecture field specifies the CPU architecture, for example Values are listed in the Go language documentation for $GOOS and ![]() #Manifest definition fullA full list of valid operating system and architecture The platform object describes the platform which the image in the The digest of the content, as defined by the Length of the retrieved content does not match the specified length, Will have an expected size for the content before validating. List references a legacy schema-1 manifest. This will generally beĪpplication/.v2+json, but it could alsoīe application/.v1+json if the manifest The manifests field contains a list of manifests for specific platforms.įields of an object in the manifests list are: This should be set toĪpplication/.list.v2+json. This field specifies the image manifest schema version as an integer. Image manifest based on the Content-Type returned in the HTTP response. A client will distinguish a manifest list from an Its use is optional, and relatively few images will The manifest list is the “fat manifest” which points to specific image manifestsįor one or more platforms. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |