Question about deprecation for gcr.io/distroless, Container Registry

[atpons]

According to https://cloud.google.com/container-registry/docs/release-notes#May_15_2023, it states that gcr.io/distroless are deprecated in Container Registry and users are required to migrate to Artifact Registry.

Do you have any plans to migration to Artifact Registry?

Thank you all for your contributing.

[loosebazooka]

I think we'll just be doing gcr.io hosted on artifact registry for a bit. But I haven't tested that out yet, but we're pretty safe for another year it looks like.

[matthewrobertson]

@loosebazooka let me know if you want some help making the transition. There is a bit of extra work for Google owned repos. My team is going through the process for a couple GCR repos we own so we have a bit of experience.

[j-windsor]

I have an issue b/297937428 impacting customers for my team that will not be fixed in GCR as it is deprecated. Is there a timeline for this?

[grassehh]

Any udpates about this ? Container Registry will be replaced by Artifact Registry on March 18, 2025.

[loosebazooka]

I'm still kinda slowly working on this. No timeline is available. But it'll get done before deprecation. We will still use the gcr.io urls.

[baraknaveh]

@loosebazooka looks like updates to gcr.io stopped coming as of March-11. Any idea why? Is there a workaround?

[loosebazooka]

Gcr.io is still serving images as far as I can tell.

[baraknaveh]

@loosebazooka still serving, but the last build creation dates are March 11

[loosebazooka]

Can you point me to what you're looking at

[baraknaveh]

EDIT: corrected the link

@loosebazooka I'm looking at https://console.cloud.google.com/gcr/images/distroless/global/base-debian12 (sorting by created time, descending).

We're experiencing a new incompatibility issue between a fully patched python:3.12-slim-bookworm and gcr.io/distroless/base-debian12 for a configuration that has been working for while now. My suspicion is that gcr.io/distroless/base-debian12 might have fallen behind on updates. Might be a red herring but the last created time of March-11 seems to align with this explanation.

[loosebazooka]

We were doing some active development around then with the distroless ruleset, those times may not be useful. "upload time" is probably what you want. You can assume at best that creation time is always some arbitrary time in the past.

[baraknaveh]

Thanks for clarifying! We'll keep investigating and I'll report back if we find anything share-worthy.