Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Beban kerja saya tidak dimulai
Saat mencoba memulai migrasi, Anda mungkin mengalami error yang
mencegah workload dimulai dengan benar.
Jika Anda mengalami error yang mencegah beban kerja dimulai dengan benar, coba langkah pemecahan masalah yang dijelaskan dalam dokumen ini sebelum menghubungi dukungan.
Menambahkan izin yang diperlukan untuk mengambil image dari Google Container Registry
Agar workload Anda dapat dimulai, cluster harus mengambil image workload dari
Google Container Registry (GCR), yang terkadang
gagal karena izin tidak ada.
Untuk mengidentifikasi masalah ini, lakukan langkah-langkah berikut:
Di Google Cloud console, buka halaman Object browser.
Dari daftar pod yang ditampilkan, temukan pod yang sesuai dengan beban kerja Anda, lalu untuk membuka detail pod, klik nama pod.
Di halaman Pod details, jika banner muncul yang menampilkan
error failed to pull and unpack image dan 403 forbidden,
izin yang diperlukan untuk mengambil image beban kerja tidak ada.
Untuk mengatasi masalah ini, lakukan langkah-langkah berikut:
Tambahkan peran
yang disebut Storage Object Viewer ke Akun layanan Compute Engine default
dalam project Anda.
Pod baru akan otomatis dibuat yang menggantikan pod yang dihapus.
Workload yang dimigrasikan sekarang seharusnya dapat diakses.
Menonaktifkan cluster GKE Autopilot
Mulai Memigrasikan ke Container, penggunaan cluster GKE Autopilot
diaktifkan secara default. Akibatnya, setiap migrasi baru yang dibuat untuk
Migrasi ke Container akan menggunakan cluster GKE Autopilot, kecuali jika ditentukan
sebaliknya.
Coba nonaktifkan cluster GKE Autopilot dan coba mulai lagi beban kerja migrasi Anda.
Untuk menonaktifkan cluster GKE Autopilot, lakukan langkah-langkah berikut untuk menetapkan
v2kServiceManager ke false:
[[["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-19 UTC."],[],[],null,["# My workload does not start\n==========================\n\nWhen attempting to start a migration, you may encounter an error that\nprevents your workload from starting correctly.\n\nIf you experience an error that prevents your workload from starting correctly,\ntry the troubleshooting steps described in this document before contacting\nsupport.\n\nAdd permissions required to pull images from Google Container Registry\n----------------------------------------------------------------------\n\nFor your workload to start, the cluster needs to pull the workload image from\n[Google Container Registry (GCR)](/container-registry), which might sometimes\nfail due to missing permissions.\n\nTo identify this issue, perform these steps:\n\n1. In the Google Cloud console, go to the **Object browser** page.\n\n [Go to Object browser](https://console.cloud.google.com/kubernetes/object/browser)\n\n \u003cbr /\u003e\n\n2. Select your cluster.\n\n3. From the **Object Kinds** list, select **Pod**.\n\n4. From the list of pods that is displayed, locate the pod corresponding to your\n workload, and then to open pod details, click the pod name.\n\n5. On the **Pod details** page, if a banner appears that displays the\n `failed to pull and unpack image` and `403 forbidden` errors,\n then the permissions required to pull the workload image are missing.\n\nTo resolve this issue, perform these steps:\n\n1. [Add a role](/iam/docs/manage-access-service-accounts#grant-single-role)\n called **Storage Object Viewer** to the **Default Compute Engine service account**\n in your project.\n\n2. Then, [delete](https://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#delete)\n the pod from your cluster.\n\n A new pod is automatically created which replaces the deleted pod.\n\nYour migrated workload should now be accessible.\n\nDisable GKE Autopilot clusters\n------------------------------\n\nAs of Migrate to Containers, use of GKE Autopilot clusters is\nenabled by default. As a result, any new migrations created for\nMigrate to Containers will use GKE Autopilot clusters unless specified\notherwise.\n\nTry disabling GKE Autopilot clusters and attempt to start\nyour migration workload again.\n\nTo disable GKE Autopilot clusters, perform these steps to set\n`v2kServiceManager` to `false`:\n\n1. [Edit your migration plan](/migrate/containers/docs/customizing-a-migration-plan#edit_the_migration_plan).\n\n 1. In the \u003cvar translate=\"no\"\u003eMIGRATION_NAME\u003c/var\u003e`.yaml` file, locate\n `v2kServiceManager` and set it to `false`.\n\n Change: \n\n v2kServiceManager: true\n\n to: \n\n v2kServiceManager: false\n\n 2. Save your file.\n\n2. [Reinitiate your migration](/migrate/anthos/docs/executing-a-migration) using Migrate to Containers.\n\nIf your workload still does not start correctly after disabling GKE Autopilot clusters,\nthen contact your support channel."]]
