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.

Sign up for GitHub

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

Jump to bottom

Custom Image returns 502 Bad Gateway #48

Closed

asongent opened this issue Sep 10, 2024 · 1 comment

Labels

bug

asongent commented Sep 10, 2024

Few things noted:

I built my own image following the steps stipulated here, but continue to receive 502 Bad Gateway. I was able to hit Swagger UI as soon as I switched the image to default.
I wondered why access was denied while I tried pulling default image to test local deployment, but was able to use it during deployment using AWS Lambda Function.

Any help with this will be greatly appreciated

asongent added the bug label

asongent changed the title ~~Custom Image returned 502 Bad Gateway~~ Custom Image returns 502 Bad Gateway

Member

zxkane commented Oct 10, 2024

The issue likely arises from building the image on x86_64, however, the Lambda/ECS require the arm64 architecture image. #58 should resolve it.

zxkane closed this as completed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment