-
Notifications
You must be signed in to change notification settings - Fork 236
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
Fail to deploy KEDA - read udp x.x.x.x:46084->y.y.y.y:53: i/o timeout on MacOS (Apple Silicon) #3377
Comments
You mean it works inside the VM? You can ssh to the VM using https://github.com/code-ready/crc/wiki/Debugging-guide document. |
@praveenkumar I mean that I can successfully pull the image directly through Podman, outside CRC. But in CRC, it is failing to pull the image with that |
This issue is not only for Keda. It is the same even for the simple NGINX deployment.
Same error to pull the image on MacOS (Apple M1 Max chip). It must be something in OpenShift CRC as it works in minikube. |
@mhcastro I tried same but didn't have issue pulling the image, have you tried following?
|
Yes, I have tried that. It works in minikube, but not in CRC. |
@mhcastro Are you trying to run |
@praveenkumar - no, I am not. |
Hi - I noticed that the error message is issued by |
@praveenkumar This seems to be a known, legitimate and recurrent issue, which is also referred by #3373. The trick seems to be in the ability to reproduce. |
This may be relevant info ....
|
@praveenkumar perhaps one additional piece of information. I didn't have issues with CRC in MacOS using Intel-chip. I started having the problems only in the |
This can be closed. It is working now after upgrading to Mac OS Ventura 13.3 on M1 chip, without any change to DNS.
and
|
General information
crc setup
before starting it? Yes.CRC version
CRC status
CRC config
- consent-telemetry : no
Host Operating System
Steps to reproduce
helm install keda kedacore/keda --namespace keda
ErrImagePull
.podman pull ghcr.io/kedacore/keda-metrics-apiserver:2.8.1
There is an issue in Linux (Issue #253) that sounds similar, but it is in Federa and the resolution may be different.
The text was updated successfully, but these errors were encountered: