New OCI manifest issue #92
Comments
|
Docker v23 supporting oci manifest docker/cli#3990 |
This comment was marked as spam.
This comment was marked as spam.
moschlar
added a commit
that referenced
this issue
Oct 30, 2023
[Full Changelog](0.7.0...1.8.0) **Breaking changes:** - The docker image registry location has been changed to the containrrr organisation: `containrrr/shepherd` **Implemented enhancements:** - armhf support [\#108](#108) - Switch to official docker image v24 [\#107](#107) ([djmaze](https://github.com/djmaze)) - Restrict runtime of "docker service update" using "timeout" [\#98](#98) ([fooflington](https://github.com/fooflington)) - Add example for usage with swarm-cronjob [\#89](#89) ([djmaze](https://github.com/djmaze)) **Fixed bugs:** - Can't update some services: no such manifest [\#105](#105) - Service gets stuck when calling "docker service update" and won't progress [\#97](#97) - fix: docker service update with `--detach=false` hangs on services wi… [\#104](#104) ([AliRezaBeitari](https://github.com/AliRezaBeitari)) - Fix defunc VERBOSE handling [\#91](#91) ([sebthom](https://github.com/sebthom)) **Closed issues:** - How does it determine if there is an update or not? [\#111](#111) - Looking for a new maintainer [\#96](#96) - New OCI manifest issue [\#92](#92) - Run service update at a fixed time [\#88](#88) - docker swarm 20.10.12 | "docker service update" requires exactly 1 argument. [\#83](#83) - Error updating service, does not exist or it is not available when using a duplicate registry [\#78](#78) **Merged pull requests:** - Add apprise type and additional error notification [\#118](#118) ([andyloree](https://github.com/andyloree)) - Rename image in docs [\#114](#114) ([moschlar](https://github.com/moschlar)) - Fix release workflow [\#113](#113) ([moschlar](https://github.com/moschlar)) - Update README.md [\#103](#103) ([andrew-dixon](https://github.com/andrew-dixon)) - ci: add basic github actions for build/release [\#101](#101) ([piksel](https://github.com/piksel)) - correct misleading description of WITH\_NO\_RESOLVE\_IMAGE [\#100](#100) ([alex-vg](https://github.com/alex-vg)) - Move example configs to their own folder [\#99](#99) ([djmaze](https://github.com/djmaze)) - Add documentation about `REGISTRIES_FILE` [\#94](#94) ([tito](https://github.com/tito)) - Minor refactoring [\#90](#90) ([sebthom](https://github.com/sebthom)) Closes: #117
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As new build image nowadays using new OCI manifest, the script that use
docker manifestcant extract information of new image. The recommended way is to usedocker buildx imagetools inspect --raw. The problem is about insecure registry, i dont really know how to make buildx imagetools use insecure registry.docker manifestdoes not work with output from buildx v0.10 docker/buildx#1509The text was updated successfully, but these errors were encountered: