Closed grumpyp closed 1 year ago
I was not able to reproduce this on my machine, i.e., Ubuntu 22.04.2 LTS
My output :arrow_down:
I am on a Macbook with a M1 chip. Someone with a Mac M1 can confirm? In general we should find a universal solution, thats why I suggest using python:3.10-bullseye
Can you try with:
apt-get install -y build-essential python-dev
Can you try with:
apt-get install -y build-essential python-dev
Good morning, same endless wheel unfortunatly.
patrickgerard ~/Documents/GitHub/gcp_scanner [main] $ docker build -t t_gcp .
[+] Building 128.7s (12/13)
=> [internal] load build definition from Dockerfile 0.0s
=> => transferring dockerfile: 915B 0.0s
=> [internal] load .dockerignore 0.0s
=> => transferring context: 2B 0.0s
=> [internal] load metadata for docker.io/library/python:3-slim-buster 0.6s
=> [1/9] FROM docker.io/library/python:3-slim-buster@sha256:6cc3e51b24c91809e9f7abf8391c8fc56c1 0.0s
=> [internal] load build context 0.1s
=> => transferring context: 546B 0.0s
=> CACHED [2/9] RUN mkdir /home/sa_scanner 0.0s
=> CACHED [3/9] COPY src/ /home/sa_scanner/ 0.0s
=> CACHED [4/9] COPY pyproject.toml /home/sa_scanner/ 0.0s
=> CACHED [5/9] COPY README.md /home/sa_scanner 0.0s
=> CACHED [6/9] WORKDIR /home/sa_scanner 0.0s
=> [7/9] RUN apt-get update 2.6s
=> [8/9] RUN apt-get install -y build-essential python-dev 23.0s
=> [9/9] RUN pip install . 102.3s
=> => # Created wheel for pyu2f: filename=pyu2f-0.1.5-py3-none-any.whl size=39401 sha256=5453b996b4
=> => # 0ec90179ba804ad4167f63626cbc13dfab9d3f9c7edcc433573507
=> => # Stored in directory: /root/.cache/pip/wheels/a0/84/f9/1676c313d1bf6c4c30f783a7c5b18648622d5
=> => # f1b2f4caf468a
=> => # Building wheel for grpcio (setup.py): started
=> => # Building wheel for grpcio (setup.py): still running...
What's your thoughts about my suggestion using python:3.10-bullseye
?
When you say endless, how long do you mean? If it is compiling some C++ libraries that could take a while.
When you say endless, how long do you mean? If it is compiling some C++ libraries that could take a while.
A bit more than 20 mins. But it works.
patrickgerard ~/Documents/GitHub/gcp_scanner [main] $ docker build -t t_gcp .
[+] Building 1293.5s (15/15) FINISHED
=> [internal] load build definition from Dockerfile 0.1s
=> => transferring dockerfile: 37B 0.1s
=> [internal] load .dockerignore 0.0s
=> => transferring context: 2B 0.0s
=> [internal] load metadata for docker.io/library/python:3-slim-buster 7.1s
=> [auth] library/python:pull token for registry-1.docker.io 0.0s
=> [1/9] FROM docker.io/library/python:3-slim-buster@sha256:6d4b1a970e49fc2c37b4ad7b71ea4396a75 0.0s
=> => resolve docker.io/library/python:3-slim-buster@sha256:6d4b1a970e49fc2c37b4ad7b71ea4396a75 0.0s
=> [internal] load build context 0.2s
=> => transferring context: 546B 0.0s
=> CACHED [2/9] RUN mkdir /home/sa_scanner 0.0s
=> CACHED [3/9] COPY src/ /home/sa_scanner/ 0.0s
=> CACHED [4/9] COPY pyproject.toml /home/sa_scanner/ 0.0s
=> CACHED [5/9] COPY README.md /home/sa_scanner 0.0s
=> CACHED [6/9] WORKDIR /home/sa_scanner 0.0s
=> CACHED [7/9] RUN apt-get update 0.0s
=> CACHED [8/9] RUN apt-get install -y build-essential python-dev 0.0s
=> [9/9] RUN pip install . 1282.0s
=> exporting to image 4.1s
=> => exporting layers 4.0s
=> => writing image sha256:2348299ecb8c6f3b08a551bf75f85722de45295c3cd12c642c3d72d9d05d942d 0.0s
=> => naming to docker.io/library/t_gcp 0.0s
Would you rather merge this, or the version I suggested? Personally said, I would cancel the run after a few min if I see it's just a Python dependency. But it works apperently.
Happy to hear any other opinions you have on this matter :)
Hi, I'd like to get this one done. How would you like to proceed @ZetaTwo ?
Basically, I'm not at all a fan of locking the version like this but I also agree that waiting 20 min for a build is very annoying. Do we know what the root cause is of this working for .10 but not .11? Is it because they have a binary distribution for the former but not the latter? I could envision something like locking to .10 for now but then at the same time open an issue to re-evaluate this after X amount of time once .11 works as well as .10.
I havn't identified the root cause as of a specific reason why it's not working but it's related to https://pypi.org/project/grpcio/.
I'll open a ticket to re-evaluation like you said. Good idea. Thanks for the head-up.
I am experiencing this issue with Python 3.8.18 on Macbook with M1 chip. CircleCI builds this image just fine, so its likely related to Apple Silicon. Reading through this thread, I don't see any clear indication of what I need to do to fix this.
Affected Component
Describe the bug
This is a known issue with
Python3.7
https://github.com/grpc/grpc/issues/24556To Reproduce
docker build -t gcp_scan .
I am willing to fix it and open a PR :)