Best practices for containerizing Python applications with Docker | Snyk
Alpine, Slim, Bookworm, Bullseye, Stretch, Jessie — Which Docker Image Should I Choose? | by Julie Perilla Garcia | Level Up Coding
GitHub - playpauseandstop/docker-python: Add poetry, pre-commit, and other dev tools for official Python slim bullseye Docker image.
python:slim-bullseye – Is affected by CVE-2005-2541 · Issue #751 · docker-library/python · GitHub
Michael Yuan on X: "A regular Python runtime image takes up 1GB+. A “slim” one is 40MB+. An equivalent @Docker + #wasm Python image running in @realwasmedge is <7MB. That is why
GitHub - peymanslh/python-image: A Python image based on python:3.11-slim- bullseye with some extra packages.
Creating a Docker Image for Python Data Science Libraries
Python — Docker image security and Trivy scan | by Anderson Magalhães | Medium
Alpine, Slim, Stretch, Buster, Jessie, Bullseye — What are the Differences in Docker Images? | by Julie Perilla Garcia | The Startup | Medium
Best practices for containerizing Python applications with Docker | Snyk
GitHub - dkshs/python_dev: A Python 3.11.6-slim-bullseye Docker image with some terminal settings.
To Virtualenv or not to Virtualenv for Docker? This is the question. | by Jarek Potiuk | Medium
Alpine, Slim, Bookworm, Bullseye, Stretch, Jessie — Which Docker Image Should I Choose? | by Julie Perilla Garcia | Level Up Coding
How to Access Future Python Versions Like 3.12 Before the Masses | by Bex T. | Towards Data Science
Long Build times using Docker Alpine images | by Rajat Jain | Medium
Have python3 using bullseye-slim · Issue #474 · docker-library/python · GitHub