Best practices for containerizing Python applications with Docker | Snyk
Container Security in AWS
Best practices for containerizing Python applications with Docker | Snyk
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
Creating a Docker Image for Python Data Science Libraries
Python — Docker image security and Trivy scan | by Anderson Magalhães | Medium
Have python3 using bullseye-slim · Issue #474 · docker-library/python · GitHub
Best practices for building Docker images for Python apps - Speaker Deck
Best practices for containerizing Python applications with Docker | Snyk
Long Build times using Docker Alpine images | by Rajat Jain | Medium
python - How do I slim down SBERT's sentencer-transformer library? - Stack Overflow
How to Access Future Python Versions Like 3.12 Before the Masses | by Bex T. | Towards Data Science
Docker image - Migrate to 3.x-slim-bullseye from 3.x-slim-buster · Issue #18190 · apache/airflow · GitHub
GitHub - playpauseandstop/docker-python: Add poetry, pre-commit, and other dev tools for official Python slim bullseye Docker image.
Quân Huỳnh on LinkedIn: #devops #docker #python #django
Python — Docker image security and Trivy scan | by Anderson Magalhães | Medium
Reducing Docker Image Size without using Alpine - Stack Overflow
CT-3009] [Bug] <Revert python from 3.11.2-slim-bullseye to 3.10.7-slim- bullseye in /docker> · Issue #8444 · dbt-labs/dbt-core · GitHub
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 - peymanslh/python-image: A Python image based on python:3.11-slim- bullseye with some extra packages.
Building Production-Ready Python Application Images with Docker | by Remo Hoeppli | The Python Project | Feb, 2024 | Medium