GCP Compute Engine VM Instance Not Starting with Custom Image Due to Disk Configuration guide
I'm trying to figure out I'm writing unit tests and I'm working on a personal project and I'm maintaining legacy code that I've looked through the documentation and I'm still confused about I tried several approaches but none seem to work. I'm working with an scenario while trying to start a Google Cloud Compute Engine VM instance that was created from a custom image. The instance keeps failing to boot, and I see the following behavior message in the console logs: `Failed to start instance: The disk 'projects/my-project/zones/us-central1-a/disks/my-custom-image-disk' has an invalid configuration.` I've created the custom image from an existing instance using the following command: ```bash gcloud compute images create my-custom-image --source-disk my-source-disk --source-disk-zone us-central1-a ``` The original instance was using a standard persistent disk type, and the custom image is supposed to replicate that configuration. However, when I attempt to start a new instance with this image, I get the behavior mentioned above. I tried specifying the disk type explicitly when creating the instance: ```bash gcloud compute instances create my-new-instance --zone us-central1-a --image my-custom-image --machine-type n1-standard-1 --boot-disk-type pd-standard ``` But it still fails to start. Additionally, I verified the image properties using: ```bash gcloud compute images describe my-custom-image ``` And it's shown as `status: READY` with the correct `sourceType`. Could there be any specific disk configuration settings that I might have missed while creating the image? Is there a way to troubleshoot this further? I'd really appreciate any guidance on this. Any help would be greatly appreciated! I'm coming from a different tech stack and learning Bash. I'd love to hear your thoughts on this. Thanks for your help in advance! The project is a service built with Bash.