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
building docker image fails on M1 #77
Comments
I've pushed a Dockerfile that successfully builds and runs on my setup (M1) on branch related to this issue. This was done by excluding CUDA libraries from PyTorch, this reduced the file size from approx 5.7 GB to 590 MB. I don't know the exact implications of this, but since we're not training on GPU on Mac anyway. Does it matter for the project? @exook @OliverWoolland |
This sounds like a good idea for the main Dockerfile too! I might be being thick though - I can't see the change which excludes CUDA libraries from the new Dockerfile? |
Ah is it the --only-root flag for poetry? |
Yes, exactly. I also changed the base image to ARM64 Python (not sure what this would imply, but seemed like good practice). I also added updates to system as well as installing poetry through Regarding the CUDA libraries, I'm not sure -- aren't they needed for the GPU acceleration for people with Nvidia GPUs (which some might have). Nonetheless, saves a ton of space... :-) |
I think a main image which is cpu only is not unreasonable! Then a GPU tag which includes the heavy stuff? I spotted the change to the poetry install command - I guess it makes it more independent of the base image used? Does away with the need for pip in the first image too. Nice |
When building the docker image on Mac M1 with command
docker build --no-cache --progress="plain" -t baler:arm .
it fails.As far as we know this is because we're using PyTorch
1.13.1
, which pulls in Nvidia Cuda toolkit. This isn't natively available for ARM processors. The build fails whenpoetry
is looking for a compatible version.Related to:
The text was updated successfully, but these errors were encountered: