You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a python environment on AWS Beanstalk. Now, my users need to use IBKR through that env, and of course I need to run multiple ibeam containers to do so.
My question is: How do I do a 'docker pull' and then do a 'docker run' on my AWS Beanstalk env ? Is there any conf file which can help me do that ? I checked out some AWS documentation, and it seems uploading this file (attached ) to my env might work to at least pull the ibeam image inside my env .. how do I do a docker run thereafter ? I'm still not clear on both fronts.
The text was updated successfully, but these errors were encountered:
raj-crec
changed the title
Query: Need to pull and run a container on AWS Beanstalk env
Query: Need to pull ibeam and run a container on AWS Beanstalk env
Nov 11, 2022
Unfortunately, I haven't used AWS Beanstalk, so I wouldn't know how to answer this specific question. It seems to be related to running any Docker image on Beanstalk rather than IBeam itself. Therefore, I'd imagine that asking on Beanstalk-related forums or Stack Overflow may be a faster way to get the answer you need. Best of luck! 👍
I'm going to close this issue due to inactivity. Thanks for your contribution and please feel free to reopen if you'd like to continue the discussion 👍
Hi,
I have a python environment on AWS Beanstalk. Now, my users need to use IBKR through that env, and of course I need to run multiple ibeam containers to do so.
My question is: How do I do a 'docker pull' and then do a 'docker run' on my AWS Beanstalk env ? Is there any conf file which can help me do that ? I checked out some AWS documentation, and it seems uploading this file (attached ) to my env might work to at least pull the ibeam image inside my env .. how do I do a docker run thereafter ? I'm still not clear on both fronts.
Dockerrun.aws.json.txt
The text was updated successfully, but these errors were encountered: