containers.image: update to 5.22.0

Dropping the patch to add docker.io search path.

Upstream strongly recommends:

* using fully qualified names
* not adding registries that allow anonymous uploads

Adding the docker.io registry to the search path, according to the
RedHat containers team, substantially decreases the security of their
tools that Void Linux distributes.

This is a breaking change. Users will need to use "docker.io/<img>" to
pull/run images from now on, or add docker.io to the search path
themselves.
This commit is contained in:
Cameron Nemo 2022-09-15 11:31:54 -07:00 committed by Michal Vasilek
parent d4bf212da1
commit eb4b406403
2 changed files with 2 additions and 13 deletions

View File

@ -1,11 +0,0 @@
--- a/registries.conf
+++ b/registries.conf
@@ -9,7 +9,7 @@
# Registries to search for images that are not fully-qualified.
# i.e. foobar.com/my_image:latest vs my_image:latest
[registries.search]
-registries = []
+registries = ['docker.io']
# Registries that do not use TLS when pulling images or uses self-signed
# certificates.

View File

@ -1,6 +1,6 @@
# Template file for 'containers.image'
pkgname=containers.image
version=5.0.0
version=5.22.0
revision=1
wrksrc="image-${version}"
conf_files="/etc/containers/registries.conf /etc/containers/policy.json"
@ -10,7 +10,7 @@ maintainer="Cameron Nemo <cnemo@tutanota.com>"
license="Apache-2.0"
homepage="https://github.com/containers/image"
distfiles="https://github.com/containers/image/archive/v${version}.tar.gz"
checksum=99440d59728ed741e6171046cf3a6a820c2e3414cd9c17ee640efd289a015c3f
checksum=5333fdb1b913250ff9f5f8bf13f986a36a82a9ef79132fc1a5d850ac95b3428d
do_build() {
mkdir -p build