Tags: sarkkine/distribution
Tags
Bug fix: 431e46 GCS: FileWriter.Size: return offset + buffer size for Writers that are not closed
Bug fix: 93e3aa GCS: FileWriter.Size: include number of buffered bytes if the FileWriter is not closed
Docker Registry v2.4.1 Bug fixes: 93d7624 Preserve author information in schema1 manifests ba672e8 When a blob upload is committed prevent writing out hashstate in the subsequent close. 96230de Add a test with a missing _manifests directory c0d3813 Move garbage collect code into storage package 011b7e4 Ensure GC continues marking if _manifests is nonexistent 0a1fcf9 Fix wording for dry-run flag in useage message for garbage collector. ed02e88 Sorting completed parts by part number for a better accordance with the S3 spec fd5a404 Add blobWrtiter.Close() call into blobWriter.Commit() 3f538ca add cn-north-1 to valid check 3330cc5 wait for DLO segments to show up when Close()ing the writer 775d096 Use correct media type for config blob in schema2 manifest 64a9727 Only check validity of S3 region if not using custom endpoint dafb59f Ensure we log io.Copy errors and bytes copied/total in uploads
What's new? New S3 storage driver The default s3 storage driver is now implemented on top of the official Amazon S3 SDK, boasting major performance and stability goodness. The previous storage is still available, but deprecated. Garbage Collector A garbage collector command has been added to the registry. Tagged Manifest Events Manifest push and pull events will now include the tag which was used in the operation (if applicable). Relative URLs The registry can now be configured to return relative URLs in Location headers. V1 Signature disabled With the ongoing adoption of the schema 2 manifest format and deprecation of signatures, this option will improve pull performance by generating and returning a single libtrust signature. Gotchas The RADOS storage driver has been removed. The registry can still be used with Ceph as the storage backend using the swift driver in conjunction with the Swift API gateway. The command line format has changed to support subcommands. To run a registry as before an additional subcommand - serve - is required. The legacy S3 storage driver, based on adroll/goamz is now deprecated and will be removed in a future release.
Merge pull request distribution#1578 from majewsky/do-not-swallow-error don't swallow errors in Swift driver's GetContent()
utulize config log format within gc Signed-off-by: Tony Holdstock-Brown <tony@docker.com>
Bug fixes: Allow uppercase characters in hostnames … 34c3acf Fix schema1 manifest etag and docker content digest header … d7eb5d1 Add option to disable signatures … d1c1730 To avoid any network use unless necessary, delay establishing authori… … 740ed69 Extend authChallenger interface to remove type cast. … 16445b6 Enable proxying registries to downgrade fetched manifests to Schema 1. … 3693621
Enable proxying registries to downgrade fetched manifests to Schema 1. Ensure Accept headers are sent with TagService.Get (which hits manifest endpoints). Add support for remote Get and Put for the proxied blobstore. Signed-off-by: Richard Scothern <richard.scothern@gmail.com>
Docker Registry v2.3.0 What’s new? This Docker Registry release is the first to support the Image Manifest Version 2, Schema 2 manifest format. This new schema version has two primary goals. The first is to move the Docker engine towards content-addressable images, by supporting an image model where the image's configuration can be hashed to generate an ID for the image. The second is to allow multi-architecture images, through a "fat manifest" which references image manifests for platform-specific versions of an image. For details, see https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md Cross Repository Blob Mount Previously the registry required all blob data to be uploaded to a repository, even if it existed in the Registry’s blob store. This was a security measure to ensure the clients owned the data they intended to upload. Cross Repository Mount now enables an existing blob to be mounted into the target repository if it already exists in a repository which the user has pull access to. This can reduce the amount of data transferred when pushing images. For details, see: distribution#634 Additionally there are a number of performance improvements, bug fixes and documentation updates. Gotchas In certain cases, pull by digest will not work. For details, see https://github.com/docker/distribution/blob/master/docs/compatibility.md
Merge pull request distribution#1394 from RichardScothern/invalidate-bdc Invalidate the blob store descriptor cache
PreviousNext