chainguard/crane
on Docker Hub
sha256-f3dbd0b87c0d980f822650a5c1804b1db7c4f870c6e91bbf1ba13313b4f93fdd.sig
chainguard/kubectl
on Docker Hub
sha256-48823f7198c7c7f08f39c6939ac13508f748d458a99bb65a3f575ecc1e3ca229.sig
sha256-10dd3538250921e9c85d94ba8fd54baf07f7372ac53f178d0caa60e963110759.sig
chainguard/crane
on Docker Hub
sha256-45cb07086a6cdaf61e88c9b94c2f65008296297ccf7b94e7daed4366668ea0e4.sig
chainguard/busybox
on Docker Hub
sha256-f3b75a16b79f84171c013c802721b0f2b38e33ab1461e0c55f8909424294f34f.sig
chainguard/helm
on Docker Hub
sha256-9396b5a639b8855e2c796f21f9cc0d68fbca51856c12bb12fd685aabe4e8703c.sig
chainguard/static
on Docker Hub
sha256-8f9c7533c7709270342660bca209e5fc593483c27f95283e1082424c1e0da967.sig
chainguard/helm
on Docker Hub
sha256-7d12bc0d7cbd833236253407688fea2d8c59507bebec9d790361304290f30b60.sig
chainguard/kubectl
on Docker Hub
sha256-aaab0870ac549b5bbbd77c947f6354099a6988d16c36b93ee6d4babc227bef18.sig
chainguard/busybox
on Docker Hub
sha256-01c4029ff15de19e67307803fa8c4e8c913f71048c854303c80cc7bbca2323d7.sig
chainguard/static
on Docker Hub
sha256-939754fefdbdb198356dc3187310417777d4dd8561be000885e224d49a4ce727.sig
chainguard/crane
on Docker Hub
sha256-b057bda32b0897dcf83eacbbaffc9ac9e1e887f03f1bdf88c7d15ca8d27b07d5.sig
chainguard/kubectl
on Docker Hub
sha256-dc9b1754977101d6c7dbd0716a57db40d532b4f35137d9b38df0633123b7c1bf.sig
chainguard/helm
on Docker Hub
sha256-efab5b845f634390ccca8e445758c1e0879c8bc126c6fb516413958c057994bd.sig
sha256-9e392450965aeaefe36241438c26addcccea908c34476fbb3e04973d0e243bed.sig
chainguard/static
on Docker Hub
sha256-fc42af33e643f20d08baf03cddcc1c02ba57052dfb02edb0d79f3fc47bcea8d9.sig
eclipse-temurin
on Docker Hub
21-jre
21-jdk-windowsservercore-ltsc2025
21-jdk-windowsservercore-ltsc2022
21-jdk-windowsservercore
21-jdk-ubi9-minimal
21-jdk-ubi10-minimal
