By using AWS re:Post, you agree to the AWS re:Post Terms of Use

Elastic Beanstalk docker application error for Python flask application

0

I am trying to deploy a flask application to elastic beanstalk via docker. When I follow the tutorials and create the application: #eb create dev-api-container I get an error: ERROR: ServiceError - Configuration validation exception: Unknown or duplicate parameter: WSGIPath

I see have found some information related to an .ebextensions file where I should set this but I am confused because if this is a docker container - does elastic beanstalk even know this is a python app?

I am stumped here for how to set/clear this flag. If I run the container locally it runs as I would expect.

I have done a default configuration and am trying to deploy this container into us-east-1. I have not configured WSGIPath for this application.

asked 2 years ago609 views
3 Answers
0

So I have recreated the sample flask application from the documentation. I am able to build, deploy and run this application in elastic beanstalk.

I have gone through and as much as possible made my environment match theirs(the sample uses an old version of python and flask). I have the same Procfile with the same wsgi configuration: web: gunicorn --bind :5000 --workers 3 --threads 2 project.wsgi:application

As far as I can see the Docker files are very similar. I don't get a lot of feedback related to the problem aside from the message: # eb create api-container-dev
Creating application version archive "app-b27b-230210_163707435120". Uploading api-container/app-b27b-230210_163707435120.zip to S3. This may take a while. Upload Complete. ERROR: ServiceError - Configuration validation exception: Unknown or duplicate parameter: WSGIPath

Are there any ways that I can get error logs from this creation sequence to isolate where the problem is?

I am also going to try some things with my code to see if I can isolate the problem.

answered 2 years ago
0

so I see deploying w/o docker you cant provide [app-name].wsgi:application if you use the eb cli. its just application now I might have to go to EC2 at this point

answered 2 years ago
0

greetings there is a bug with beanstalk, you need to use the eb cli to deploy the basic app exactly as you see it from the docs, then update all the env vars and configs from there, once then use the eb cli to deploy your actual app, everything you want to make updates you need to deploy the dummy to make changes

answered 2 years ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions