ERROR: Could not find a version that satisfies the requirement google-python-cloud-debugger==2.18 (from versions: none)

Describe the bug

I want to deploy on my local minicube, but when I run the skaffold run command , at the step: Step 7/11 : RUN pip install -r requirements.txt the output shows:

ERROR: Could not find a version that satisfies the requirement google-python-cloud-debugger==2.18 (from versions: none)
ERROR: No matching distribution found for google-python-cloud-debugger==2.18.

I don’t know how to handle this as a k8s beginner, and I have tried to use the v0.3.6 but it still doesn’t work.

Environment

• minikube version: v1.25.2
• Docker version 20.10.14
• macOS Monterey 12.3.1
• Apple M1 arm64

Logs

Screenshots

Additional context

Exposure

[NimJay]

I was just able to successfully docker build the recommendationservice on my local machine:

➜  recommendationservice git:(main) docker build . -t delete-me
[+] Building 35.4s (12/12) FINISHED
 => [internal] load build definition from Dockerfile                                             0.0s
 => => transferring dockerfile: 40B                                                              0.0s
 => [internal] load .dockerignore                                                                0.0s
 => => transferring context: 2B                                                                  0.0s
 => [internal] load metadata for docker.io/library/python:3.7-slim                               1.2s
 => [internal] load build context                                                                0.0s
 => => transferring context: 811B                                                                0.0s
 => [1/7] FROM docker.io/library/python:3.7-slim@sha256:7e5cc927e64e6fd18aefe4a93a2727e1d4a1eac  1.6s
 => => resolve docker.io/library/python:3.7-slim@sha256:7e5cc927e64e6fd18aefe4a93a2727e1d4a1eac  0.0s
 => => sha256:7e5cc927e64e6fd18aefe4a93a2727e1d4a1eac1f4e90ecb6c0b12b7655ce72d 1.86kB / 1.86kB   0.0s
 => => sha256:2c4358955e040a91882502a23abf06440d871ad786fa4452423c6e50cbb4e632 1.37kB / 1.37kB   0.0s
 => => sha256:753fa96239cd770bf2081db829354129e91cf4a2a55017efffb98a25b15f4a1c 8.17kB / 8.17kB   0.0s
 => => sha256:fa7d81b69b9af8e7d8748b3d3ccc7a4dd28dd7752c0e118ad1f3238d3b5f1ee6 1.08MB / 1.08MB   0.2s
 => => sha256:2fd9be6893d2407bd5f8599c7e87dd68cb930fe776a077496cb04ca2aacabf1 10.73MB / 10.73MB  0.8s
 => => sha256:7c8f45ffebd67f9142e302221827e7964e260aa7da0353362a507c2d00237e9e 233B / 233B       0.2s
 => => extracting sha256:fa7d81b69b9af8e7d8748b3d3ccc7a4dd28dd7752c0e118ad1f3238d3b5f1ee6        0.1s
 => => sha256:b781a207dc07f23b0cba5d774cc9e1f15251640154db6f10348dd53581aee417 3.17MB / 3.17MB   0.6s
 => => extracting sha256:2fd9be6893d2407bd5f8599c7e87dd68cb930fe776a077496cb04ca2aacabf19        0.4s
 => => extracting sha256:7c8f45ffebd67f9142e302221827e7964e260aa7da0353362a507c2d00237e9e        0.0s
 => => extracting sha256:b781a207dc07f23b0cba5d774cc9e1f15251640154db6f10348dd53581aee417        0.2s
 => [2/7] RUN apt-get update -qqy &&  apt-get -qqy install wget g++ &&  rm -rf /var/lib/apt/li  13.8s
 => [3/7] RUN GRPC_HEALTH_PROBE_VERSION=v0.4.11 &&     wget -qO/bin/grpc_health_probe https://g  1.4s
 => [4/7] WORKDIR /recommendationservice                                                         0.0s
 => [5/7] COPY requirements.txt requirements.txt                                                 0.0s
 => [6/7] RUN pip install -r requirements.txt                                                   15.7s
 => [7/7] COPY . .                                                                               0.0s
...

• I have deprioritized this issue from p1 to p2, but I think this is still a critical issue.
• @ckim328 and I wonder if this is related to the fact that you’re using Apple’s M1 chip. We have faced M1-related issues in the past (e.g. in #622).
• Another related discussion about the Could not find ... google-python-cloud-debugger==2.18 error: https://github.com/GoogleCloudPlatform/cloud-debug-python/issues/20

[JBHua]

I’ve encountered the exact same problem using Apple’s M1 Chip (Mac Studio). I suspect it is either due to the chip architecture (ARM64) or macOS (see this reply.)