Be notified of new releases
Create your free GitHub account today to subscribe to this repository for new releases and build software alongside 50 million developers.Sign up
This is a small point release to fix a bug that apparently was introduced pre-v1.0.0, but due to differences in how registries handled the location of manifest references the issue did not present itself until recently with a team utilizing Artifactory to store multi-platform images.
Pre-packaged Docker images have been updated to this release on DockerHub:
This small bug-fix release includes a performance/potential bug fix enhancement to not pull the entire tag list for an image during inspect (which also happens during push of a manifest list as the image must be inspected to get the manifest(s) contents). For images with significantly large tag counts this was sometimes producing an error (reported in #84), and was always impacted performance.
Given tags were provided in the
--raw output, the fix from @ibuildthecloud in #90 will continue to provide the tags in case a tool was using the
--raw output to scrape tag information from an image, but for uses of the tool without specifying
--raw will no longer pull all tags.
This release's builds were performed with Golang v1.13.9.
The v1.0.1 release updates the Golang version to 1.13.8, the latest supported Golang 1.13 point release to fix an issue with running on s390x (#87). This release also contains a few minor updates to vendored packages, updates the AppVeyor configuration, and fixes the Windows
Dockerfile to match the current state of the art with respect to Windows containers and the nanoserver image releases since the 1.0.0 release.
This is the official v1.0.0 release of manifest-tool!
Other than time passing, no code changes were introduced since the rc3 release in April 2019.
This release was built with the newly released Go 1.13 toolchain, and all scripts/CI tools were updated to this latest release. Since rc2, an official DockerHub multi-platform supporting image has been created automatically for each release tag, and this now includes a v1.0.0 tagged image for manifest-tool.
The v1.0.0-rc3 release candidate is expected to be the final release candidate for manifest-tool to reach v1.0.0.
The only fix since rc2 is a more correct implementation of the
--insecure flag that handles the fact that setting the insecure registries list is not working as expected in the imported registry API.
This fix was merged via PR #77.
As noted in the v1.0.0-rc2 release notes, there is now a standard DockerHub-hosted image of
manifest-tool which now has been updated to rc3. See more details about this image on DockerHub.
This v1.0.0-rc2 release is the second release candidate of manifest-tool. A few useful fixes have gone into
manifest-tool based on feedback since the first release candidate.
In addition to the binaries and signatures available below for download, there is now a multi-platform DockerHub-hosted image of
manifest-tool at the v1.0.0-rc2 level. You can find the image at mplatform/manifest-tool:v1.0.0-rc2, which is also currently pointed to by the latest tag until the next release. The architecture/platform support for this image is listed below:
$ docker run --rm mplatform/mquery mplatform/manifest-tool:latest Image: mplatform/manifest-tool:latest * Manifest List: Yes * Supported platforms: - linux/amd64 - linux/arm - linux/arm64 - linux/ppc64le - linux/s390x - windows/amd64:10.0.14393.2312
Noted fixes since the first release candidate:
- #70: Add support for insecure registries
- #75: fix inspect output to show layers of v1 media type images (thanks to @tianon for the bug report)
- #72: Adds support for variant (with some minor limitations) in the template-style use of the tool; thanks @ekristen for providing this feature; future plans may use Go text templates for better support/capabilities
Please report any issues with this release ASAP as a v1.0.0 is coming soon barring any known problems.
This is a release candidate of
manifest-tool in preparation for a v1.0.0 release. The only change since v0.9.0 is the re-vendoring of all the core upstream packages/APIs to fix an issue that was solved in the
docker/distribution code since the original vendoring.
Thanks to @erwinkersten for reporting the issue with Azure registry, and to @JoshEbersol and @jhowardmsft for the debug and pointing out the simple fix of re-vendoring to pick up an existing distribution code fix.
This brings the imported capabilities in line with the modern
moby/moby codebases, similar to the Docker 18.09 release. It should have zero impact on existing
manifest-tool functionality, and has been tested against several public cloud registries, DockerHub, and also by the official images team (thanks @tianon). However, in the abundance of caution, I'm releasing this update as a release candidate and will allow a few weeks for any further testing by those who depend on
manifest-tool in their environments. Please report any found issues with this RC and I will attempt to solve them prior to releasing the final v1.0.0.
A minor release that includes the recognition of the
windows/arm OS/architecture pair, due to work by the Microsoft Windows & ARM community to have a valid target for 32-bit ARM CPUs of the Windows OS.
A small release to officially pick up two recent useful fixes for 3rd party registries:
Release v0.7.0 has no significant functional changes for most users, but includes fixes that make it more useful for production activities that are already being done with branches or pre-release copies of
- Thanks to @rn,
manifest-toolcan be used with a 3rd party notary client to officially sign manifest list objects in a registry.
manifest-toolnow outputs the size of the canonical JSON in the successful push output after the digest SHA (#45)
- @avian2 cleaned up the use of ldflags in the
- @tianon added full support for ARM variants in the
make crosstarget by using proper
GOARMflags, and generally making
hack/cross.sha lot better :) in #51
Makefilecleanups around having a separate
statictarget and allowing
make binaryto be used for a normal dynamically linked binary; and using Golang 1.9.1 release for in-container builds and noting this via README content additions ( #48 and #51)
- Allowing push to
library/xxxtargets to allow @tianon and official image builders to push official content (#49)
- Tags documentation in README from @tianon (#44)
- Test script for testing Docker v2 API conforming registry support for manifest lists (#39)
Note that official release binaries now have v5, v6, and v7 arm32 variants as well an i386 Linux variant added to the rest of the architecture support already in prior releases.