24
ELI5 Using python virtual environment in docker container. (programming.dev)
submitted 2 weeks ago* (last edited 2 weeks ago) by alexdeathway@programming.dev to c/python@programming.dev
19 comments fedilink hide all child comments

I read some articles about using a virtual environment in Docker. Their argument are that the purpose of virtualization in Docker is to introduce isolation and limit conflicts with system packages etc.

However, aren't Docker and Python-based images (e.g., python:*) already doing the same thing?

Can someone eli5 this whole thing?

you are viewing a single comment's thread
view the rest of the comments
[-] uthredii@programming.dev 2 points 2 weeks ago

upgrading your base image won’t affect your python packages

Surely if upgrading python will affect your global python packages it will also affect your venv python packages?

you can use multi stage builds to create drastically smaller final images

This can also be done without using venv's, you just need to copy them to the location where global packages are installed.

[-] sweng@programming.dev 3 points 2 weeks ago

Upgrading the base image does not imply updating your python, and even updating your python does not imply updating your python packages (except for the standard libraries, of course).

[-] uthredii@programming.dev 1 points 2 weeks ago

Sure, but in the case where you upgrade python and it affects python packages it would affect global packages and a venv in the same way.

[-] sweng@programming.dev 1 points 2 weeks ago

Sure If that happens. But it may also not. Which is actually usually the case. Sure, it's not 100% safe, but it is safer.

this post was submitted on 04 Sep 2024
24 points (90.0% liked)

Python

6229 readers
48 users here now

Welcome to the Python community on the programming.dev Lemmy instance!

📅 Events

October 2023

November 2023

PastJuly 2023

August 2023

September 2023

🐍 Python project:
💓 Python Community:
✨ Python Ecosystem:
🌌 Fediverse
Communities
Projects
Feeds

founded 1 year ago
MODERATORS
erlingur@programming.dev
jnovinger@programming.dev