Default pushes image to wrong project

In Google cloud, I had an old project ( myproj-test-302801 ), I blew it away and started a new one ( myproj-307522 ). But now every time I try and push my image I get...

$ gcloud.cmd compute instances update-container myproj-test --container-image=gcr.io/myproj-307522/myproj:0.8  ERROR: (gcloud.compute.instances.update-container) NOT_FOUND: The resource 'projects/myproj-test-302801' was not found  

In other words, its like its finding my old project (myproj-test-302801) from who-knows where, and insisting on using it.

I have the project config set ok...

gcloud projects list  PROJECT_ID                NAME              PROJECT_NUMBER  myproj-307522             myproj            996908104657  

I've tried setting it again..

gcloud config set project myproj-307522  

If I push with the --project flag it works...

$ gcloud.cmd compute instances update-container myproj-test --container-image=gcr.io/myproj-307522/myproj:0.8 --project=myproj-307522  

or the environment variable also works..

$ CLOUDSDK_CORE_PROJECT=holder-307522 gcloud.cmd compute instances update-container myproj-test --container-image=gcr.io/myproj-307522/myproj:0.8  

I've looked through every config file I can find, I've done

gcloud config list  

I've looked in /c/Program Files (x86)/Google/Cloud SDK/google-cloud-sdk/properties and /c/Users/chris/.config/gcloud/configurations/config_default, I've tried starting again with

gcloud init  

and I can see no references anywhere to my old project name myproj-test-302801. I've checked that my images exist and are being uploaded to the new project's container registry. In short, the old project has gone, but gcloud still insists on using it unless I'm explicit with the --project flag.

Any ideas?

https://stackoverflow.com/questions/66621000/default-pushes-image-to-wrong-project March 14, 2021 at 12:07PM