Container Registry tidak digunakan lagi. Mulai 18 Maret 2025, Container Registry akan dinonaktifkan dan penulisan image ke Container Registry tidak tersedia. Untuk mengetahui informasi selengkapnya tentang penghentian penggunaan Container Registry dan cara melakukan migrasi ke Artifact Registry, lihat Penghentian penggunaan Container Registry.
Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Container Registry tidak digunakan lagi. Mulai 18 Maret 2025,
Container Registry akan dihentikan dan penulisan image ke Container Registry tidak akan tersedia.
Penonaktifan Container Registry
Penutupan dijadwalkan sebagai berikut:
Mulai 18 Maret 2025, penulisan image ke Container Registry tidak tersedia.
Setelah 3 Juni 2025, membaca image dari Container Registry tidak akan tersedia. Image yang ada di Container Registry tidak dapat diakses.
Mulai 14 Oktober 2025, jika Anda telah menyelesaikan langkah-langkah untuk menyiapkan
repositori gcr.io di Artifact Registry, maka
pengiriman ke endpoint gcr.io akan menyimpan image di Artifact Registry dan semua
URL gcr.io akan ditayangkan dari Artifact Registry. Semua image di Container Registry yang belum disalin ke Artifact Registry tidak tersedia.
Beralih ke Artifact Registry
Bergantung pada cara Anda mengonfigurasi dan menggunakan Container Registry, Anda mungkin perlu melakukan beberapa langkah konfigurasi untuk menyiapkan project baru agar berhasil menangani permintaan ke domain gcr.io. Misalnya, akun utama yang mengakses
repositori harus memiliki peran Artifact Registry yang sesuai atau peran dengan
izin yang setara.
Sebaiknya Anda mentransisikan project dengan penggunaan Container Registry yang aktif ke repositori Artifact Registry. Lihat Melakukan transisi dari Container Registry
untuk mempelajari perbedaan fitur dan opsi transisi.
Menggunakan alat transisi kami
Gunakan alat berikut untuk memeriksa project mana yang menggunakan Container Registry, menyalin image dari Container Registry ke Artifact Registry, dan otomatis memigrasikan beberapa project dari Container Registry ke Artifact Registry.
Gunakan alat migrasi kami untuk memigrasikan project dari Container Registry ke Artifact Registry, menyalin image, dan memilih jenis repositori transisi yang Anda inginkan.
Batasan berikut diterapkan sebagai bagian dari pendekatan bertahap kami untuk menghentikan Container Registry:
Mulai 18 Maret 2025, penulisan image ke Container Registry tidak tersedia.
Mulai 8 Januari 2024, di organisasi yang belum pernah menggunakan Container Registry sebelumnya, dan di project yang bukan milik organisasi, semua repositori gcr.io baru dihosting di Artifact Registry secara default.
Mulai 15 Mei 2024, project Google Cloud yang sebelumnya tidak menggunakan Container Registry hanya mendukung repositori gcr.io yang dihosting di Artifact Registry.
Mulai 15 Mei 2023, Container Registry tidak digunakan lagi.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-08-11 UTC."],[[["\u003cp\u003eContainer Registry is being shut down, with writing images unavailable after March 18, 2025, and reading images unavailable after May 20, 2025.\u003c/p\u003e\n"],["\u003cp\u003eAfter July 17, 2025, \u003ccode\u003egcr.io\u003c/code\u003e endpoints will store images in Artifact Registry if the setup is complete, and any images not copied from Container Registry will be inaccessible.\u003c/p\u003e\n"],["\u003cp\u003eTransitioning to Artifact Registry is recommended for active Container Registry users, and it requires certain configuration steps, such as appropriate role assignment.\u003c/p\u003e\n"],["\u003cp\u003eTools are available to check Container Registry usage, copy images, and migrate projects to Artifact Registry.\u003c/p\u003e\n"],["\u003cp\u003eNew \u003ccode\u003egcr.io\u003c/code\u003e repositories in organizations and projects without prior Container Registry use are already hosted on Artifact Registry, as of January 8, 2024, and as of May 15, 2024 projects without previous usage of Container Registry only support \u003ccode\u003egcr.io\u003c/code\u003e repositories hosted in Artifact Registry.\u003c/p\u003e\n"]]],[],null,["# Container Registry deprecation\n\nContainer Registry is deprecated. Effective March 18, 2025, Container Registry is shut down and writing images to Container Registry is unavailable.\n\n\u003cbr /\u003e\n\nContainer Registry shutdown\n---------------------------\n\nThe shutdown is scheduled as follows:\n\n- Effective March 18, 2025, writing images to Container Registry is unavailable.\n- After June 03, 2025, reading images from Container Registry is unavailable. Existing images in Container Registry are inaccessible.\n- Effective October 14, 2025, if you have completed the steps to set up [`gcr.io` repositories](/artifact-registry/docs/transition/gcr-repositories) in Artifact Registry, then pushing to `gcr.io` endpoints stores images in Artifact Registry and all `gcr.io` URLs are served from Artifact Registry. Any images in Container Registry that haven't been copied to Artifact Registry are unavailable.\n\nTransition to Artifact Registry\n-------------------------------\n\nDepending on how you configure and use Container Registry, you might\nneed to perform some configuration steps to prepare a new project to successfully\nhandle requests to the `gcr.io` domain. For example, principals that access\nthe repositories must have an appropriate Artifact Registry role or a role with\nequivalent permissions.\n\nWe recommend that you transition projects with active Container Registry usage to\nArtifact Registry repositories. See [Transition from Container Registry](/artifact-registry/docs/transition/transition-from-gcr)\nto learn about feature differences and transition options.\n\nUse our transition tooling\n--------------------------\n\n| **Warning:** After June 03, 2025, if you haven't transitioned to Artifact Registry, then images in Container Registry are inaccessible.\n\nUse the following tools to check which projects have Container Registry usage,\ncopy images from Container Registry to Artifact Registry, and automatically migrate\nmultiple projects from Container Registry to Artifact Registry.\n\n- [Check Container Registry usage](/artifact-registry/docs/transition/check-gcr-usage).\n- Use our [migration tool](/artifact-registry/docs/transition/auto-migrate-gcr-ar) to migrate projects from Container Registry to Artifact Registry, copy images, and select your preferred transition repository type.\n\nWe will continue to communicate changes to the service in accordance with the\n[Google Cloud terms of service](/terms).\n\nContainer Registry deprecation history\n--------------------------------------\n\nThe following restrictions were implemented as part of our phased approach to\ndiscontinuing Container Registry:\n\n- Effective March 18, 2025, writing images to Container Registry is unavailable.\n- Effective January 8, 2024, in organizations that haven't used Container Registry before, and in projects that don't belong to organizations, all new `gcr.io` repositories are hosted on Artifact Registry by default.\n- Effective May 15, 2024, Google Cloud projects without previous usage of Container Registry only support `gcr.io` repositories hosted in [Artifact Registry](/artifact-registry/docs).\n- Effective May 15, 2023, Container Registry is deprecated."]]
