-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Atlantis v0.18.1 Docker Builds do not run on ECS/Fargate ARM Graviton #2001
Comments
Are we good to close this? |
Let me test new version and confirm working. |
@nishkrishnan Was there a reason this should be closed? The issue still exists. Reconfirmed and nothing in the 0.18.2 changelog suggests this has been fixed. |
@chenrui333 Any chance you'd be able to take a look at this? |
Thanks to your comment, @chenrui333, I realised the base image doesn't take different architectures into account. I have tried to fix that in #2099 which might be what is needed for getting the Docker image working correctly on ARM machines. |
Thank you so much! Looking forward to trying this soon as as the next release is cut ! |
@chenrui333 Confirmed it works in ECS / Fargate / ARM64 👏 👏 Feel free to mark issue as resolved. Side note: Version reported in lower right as |
oh shit, that is my bad, I used 0.18.6 and decided to bump it to 0.19.0. Either way, glad it works now. 👍 |
Will fix it in next week. Thanks! :) Closing the issue now. |
Summary
Using the latest Atlantis v0.18.1 docker builds result in errors when running on ARM ECS/Fargate. I tested using the following container image
ghcr.io/runatlantis/atlantis:latest@sha256:66d431df3cd1893175abf7133aeef96f9ab212a3c260daf8ef2a54042259f503
in ECS/Fargate that is set to run in ARM. This results in the following output:
standard_init_linux.go:228: exec user process caused: exec format error
Referenced ECS Task Definition (Sensitive values masked)
Task Definition
Community Note
The text was updated successfully, but these errors were encountered: