How to make your Python Docker images secure, fast & small

In the world of microservices, having secure, efficient, and compact <a href="https://www.docker.com/" rel="noopener ugc nofollow" target="_blank">Docker</a> images is crucial for successful deployments. This blog will explore the key factors that contribute to building such images, including the importance of not running images as the root user, updating and upgrading packages when building the image, considering Docker’s layer architecture while writing Dockerfile instructions, and utilizing multistage builds to decrease your image size. Parts of this blog were inspired by a great talk that I recently from Matthijs Brouns, which you can view <a href="https://www.youtube.com/watch?v=kx-SeGbkNPU" rel="noopener ugc nofollow" target="_blank">here</a>. I will be using the CLI tool <a href="https://github.com/wagoodman/dive" rel="noopener ugc nofollow" target="_blank">Dive</a> to analyze the image and its layers. The aim of the Docker image is to serve as a host for a <a href="https://fastapi.tiangolo.com/" rel="noopener ugc nofollow" target="_blank">FASTAPI</a> server for a machine learning application, with Poetry as its dependency manager. For more information on the motivation to use Poetry instead of pip/pipenv/pip-tools/conda, read <a href="https://andrewbrookins.com/python/why-poetry/" rel="noopener ugc nofollow" target="_blank">this</a> and <a href="https://betterprogramming.pub/5-reasons-why-poetry-beats-pip-python-setup-6f6bd3488a04" rel="noopener ugc nofollow" target="_blank">this</a> blog. Please note that a basic understanding of Docker and <a href="https://docs.docker.com/engine/reference/builder/" rel="noopener ugc nofollow" target="_blank">Dockerfiles</a> is a prerequisite for this article. <a href="https://medium.com/vantageai/how-to-make-your-python-docker-images-secure-fast-small-b3a6870373a0">Website</a>