emmyN:


Boss, do you use Docker?

Yes alot, I love it, I recently deployed a NodeJS and Spring boot application with it on heroku

qtguru:


Yes alot, I love it, I recently deployed a NodeJS and Spring boot application with it on heroku

Okay. I am very new to it and required to develop an application using it with Python for a programming test. I am hoping you would be able to help with some directions as I am stuck right now.

emmyN:


Okay. I am very new to it and required to develop an application using it with Python for a programming test. I am hoping you would be able to help with some directions as I am stuck right now.

Docker is basically just to ensure you have an image that has everything to run your python app, so you'll mostly likely need an image that comes pip and python tools installed and deploying, you can take existing Dockerfiles online.

qtguru:


Docker is basically just to ensure you have an image that has everything to run your python app, so you'll mostly likely need an image that comes pip and python tools installed and deploying, you can take existing Dockerfiles online.

I am bordered about the size of the image I have. Like I only just installed flask, transformers, and torch. The build size is 6GB and took almost 2 hours to set up. So I'm wondering if this is normal, or maybe I am missing something.

2. Do you have to run docker compose up --build everytime you update your application? Like I have a container running already and then made some changes to my code. Do I go the whole docker compose route all over again to get this change to be reflected in my image?