Doesn’t docker for windows run containers in a vm More on reddit.com

Is there any docker image available which comes with pre installed python and pip. I am quite new to docker. More on forums.docker.com

Get rid of poetry for uv, you will reduce you build speeds by quite a bit since poetries dependency resolver can be pretty slow in many cases. Also stop using virtualenvs inside of the container. They just waste space since the official Python images already have a dedicated "non-system" Python pre-installed in /usr/local (and it should not matter if you used the system Python really since the container should be single purpose). More on reddit.com

As others have pointed out, I would run your app and Nginx in two separate containers. I would also use something like gunicorn to run your app in production. My favorite Python Docker images are the Python Slim images (e.g., python:3.7-slim). I find them to be a good tradeoff between small size and required packages. The base image is Debian Linux. Since you are interested in running in production you also want to be sure you are not running your Python app as root. Here is a sample Dockerfile that I use to accomplish this which you can use as a starting point (note: my app is in a folder called ./service): FROM python:3.7-slim # Get the version from the build arguments: # --build-arg VERSION=1.2.0 ARG VERSION ENV VERSION=$VERSION # Create a regular user for production RUN groupadd -g 1001 prod && \ useradd -r -u 1001 -g prod prod # Set up the development environment WORKDIR /app # Install dependencies COPY requirements.txt . RUN pip install -U pip && \ pip install --no-cache-dir -r requirements.txt # Copy the application files COPY config.py manage.py ./ COPY service ./service # Expose any ports the app is expecting in the environment ENV PORT 5000 EXPOSE $PORT # Become a regular user that owns the app folder RUN chown -R prod:prod /app USER prod # Run the service with gunicorn ENV GUNICORN_BIND 0.0.0.0:$PORT CMD ["gunicorn", "--workers=4", "--log-level=info", "service:app"] Note that I have included a build argument call VERSION. I use this in my logs so that I know what version of the app is running. You would add it to the build it like this: docker-compose build --build-arg VERSION=1.2.0 Then just pull VERSION out of the environment and display it in the log messages at startup. Don't forget to add lots of log messages in your code. When you're in production, your logs are the only thing to tell you what's going on when nothing is going right. ;-) More on reddit.com