-
Notifications
You must be signed in to change notification settings - Fork 111
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Run App on Local Cloud Run Emulator fails on ARM64 / M1 Mac #894
Comments
Hello! Apologies to hear you're hitting this friction (and sorry that it took some time to get back to you!) I'll bounce this over to the broader team for an investigation and one of us will get back to you ASAP! Feel free to keep us posted on anything else you may notice in the meantime. Thanks! |
Hi, have the same problem here. |
@davidponder It would be really nice if cloud-code could optionally use an existing local Kubernetes cluster, like k3d, as minikube occasionally causes problems, at least on macOS. |
Any updates or workarounds for this? I am also running into this issue. |
Hello! @esteluk I'm curious, what version of minikube do you have installed in the cloud code environment? you should be able to use the vscode terminal and issue 'minikube version'. Unfortunately currently we only support minikube for the cloud run local dev scenario |
Hey @glouischandra, thanks for replying! It's v1.32.0 |
Same problem here on windows |
I have the same problem. Was this ever resolved? |
@rhughes66degrees
Notes:
|
Environment:
(Hint: "Report Extension Issue on Github" command will fill these out for you.)
^ This command doesn't seem to exist. The "Report Bug" option offers a lot of logs, but none seem entirely relevant to this section.
Version information
Cloud Code Extension version: v2.7.1
VSCode version: 1.88.0
OS: MacOS 14.3.1
Cloud SDK: 471.0.0
Skaffold: 2.9.0
Kubectl: 1.26.15
Description:
I have a trivial Cloud Run application, and when trying to "Run on a cloud run emulator" (or Debug), the resulting image inevitably fails to deploy.
I don't have a strong golang/GCP background, so apologies if I'm being dumb. (I suspect this may be the case, given that I'd have assumed someone else would have encountered this issue if it did exist in this way.
launch.json:
The detailed log are:
The readiness check certainly fails to execute as expected.
When running the recommended command it returns:
The output of
gcloud alpha code export --readiness-probe --service-name backend-app --image backend-app --no-skaffold-file --dockerfile= --kubernetes-file temp/pods_and_services.yaml --env-vars K_SERVICE=backend-app,K_REVISION=local,K_CONFIGURATION=backend-app --memory 256Mi --quiet --verbosity warn
provides a Kubernetes file with a readiness probe:But the Ubuntu 18.0.4 image doesn't seem to be multi-arch - the readiness probe is never able to successfully start.
If I manually update the image to
ubuntu:22.04
and run Skaffold manually (using the generatedskaffold.yaml
) the service deploys as expected.Repro step:
The text was updated successfully, but these errors were encountered: