- Newest
- Most votes
- Most comments
Does it work locally? (is this an AWS issue or a docker compose issue) I would simplify down as much as possible until it works, then build in extra features. Looks like you have both custom networks defined as well as "links" in your Flask API definition. Looks like "links" is deprecated and I don't think you need that if you're defining custom networks.
One other thing to check is make sure there is no architecture mis-match. Your cluster is not running arm64 is it?
That error is most likely arising from a mismatch between the architecture the container was build on vs. the architecture you are running it on. To resolve this, if you are using docker take advantage of the docker buildx command. An example of this would be:
docker buildx build --platform=linux/amd64 -t somecontainer .
Replace the linux/amd64 with the architecture you wish to run your container on and it will build for that specific architecture.
Hi, thanks for the assistance. I did build the image on three architectures. It is again running locally but now gives me a different error when I attempt to run it on ECS. I used the below command to create the image
docker buildx build --platform linux/arm64,linux/amd64,linux/amd64/v2 -t dockerelvis/awsflask:latest --push .
I did create images using one of each of the above platforms but all throw same error. unable to locate files in the container.
Error: 'gunicorn_config.py' doesn't exist
GitHub repo: https://github.com/Elvis-aws/FlaskAWSApp
Help will be much appreciated, thanks
Relevant content
- asked 3 years ago
