-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Bug: docker with aws' sam build
on M1 for amd64 cannot build
#7598
Comments
Hi @stationname, thanks for reporting the issue and providing how you managed to get it to work. Marking it as needs more investigation to see if this is a sam or docker issue. |
+1 |
1 similar comment
+1 |
Example debug output 2024-12-24 01:22:38,708 | Config file location: /Users/arvindh/cs/projects/kp-restructure/lmsys/samconfig.toml Build Failed |
Disclaimer
This issue is merely for reference purposes. It's not necessarily intended to be used as triaging for fixing.
Reason: This might be a difficult edge case and I don't have a from-scratch-like clean environment to make sure the steps will lead to a failure.
Description:
Docker build fails when triggered by AWS'
sam build
on Mac M1 with target amd64 (cross-plattform).Error:
Build Failed Error: NotFound: content digest sha256:[...]: not found
Notes:
docker build
.Workaround stated at the bottom.
Steps to reproduce:
Files
*template.yaml`
Dockerfile
(↑ I hope I didn't strip too much)
app.py
samconfig.toml
Command to run
Note:
Observed result:
Error output:
Build Failed Error: NotFound: content digest sha256:[...]: not found
I can't reproduce the debug output, because I already workaround-ed the problem. 🙏
Expected result:
Build should succeed.
Additional environment details (Ex: Windows, Mac, Amazon Linux etc)
sam --version
: version 1.125.0sam --info
Workaround
Downgrade to Docker 4.7, downloadable here: https://desktop.docker.com/mac/main/arm64/77141/Docker.dmg
( @docker maintainers: Please don't remove the download link in order to keep the workaround working 🙏 )
The text was updated successfully, but these errors were encountered: