Skip to content

chore: upgrade controller-runtime package - #851

Merged
Zhiying Lin (zhiying-lin) merged 1 commit into
Azure:mainfrom
zhiying-lin:upgrade-packages-1
Jun 17, 2024
Merged

Zhiying Lin (zhiying-lin) merged 1 commit into
Azure:mainfrom
zhiying-lin:upgrade-packages-1

Conversation

@zhiying-lin

Copy link
Copy Markdown
Contributor

Description of your changes

upgrade controller-runtime package to fix CVEs

Fixes #

I have:

  • Run make reviewable to ensure this PR is ready for review.

How has this code been tested

Special notes for your reviewer

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We need to look at the hard coded replace items

@zhiying-lin
Zhiying Lin (zhiying-lin) merged commit a9c1d6c into Azure:main Jun 17, 2024
@zhiying-lin
Zhiying Lin (zhiying-lin) deleted the upgrade-packages-1 branch June 17, 2024 05:30
Britania Rodriguez Reyes (britaniar) pushed a commit that referenced this pull request Sep 2, 2026
The setup-qemu target added in #745 pinned the MCR qemu-user-static
mirror to sha256:cb0dff99, which no registry can serve:

  docker: Error response from daemon: manifest for mcr.microsoft.com/
  mirror/docker/multiarch/qemu-user-static@sha256:cb0dff99... not found:
  manifest unknown

The image has no manifest list, upstream or mirrored. When a request
carries no Accept header, or names only the manifest-list media type,
MCR answers with a deprecated schema-1 `v1+prettyjws` view synthesised
on demand from the schema-2 manifest. The digest that view advertises is
stable, but it is never stored as a manifest revision, so fetching by it
404s:

  GET  /manifests/7.2.0-1  (Accept: manifest.list.v2)  -> cb0dff99, v1+prettyjws
  GET  /manifests/sha256:cb0dff99...                   -> HTTP 404
  GET  /manifests/7.2.0-1  (Accept: manifest.v2)       -> fe60359c, schema 2
  GET  /manifests/sha256:fe60359c...                   -> HTTP 200

Repin to the real schema-2 manifest (linux/amd64, entrypoint /register),
which is all setup-qemu needs since the QEMU_IMAGE branch runs only when
TARGET_ARCH is amd64. The new digest is the one Docker Hub also serves
for multiarch/qemu-user-static:7.2.0-1, so the mirror and upstream agree.

Document how to obtain the digest, and which tools report it correctly,
so the next version bump does not reintroduce the schema-1 value.

Signed-off-by: Yetkin Timocin <ytimocin@microsoft.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants