ELI5 Using python virtual environment in docker container. (programming.dev)

submitted 2 months ago* (last edited 2 months ago) by alexdeathway@programming.dev to c/python@programming.dev

20 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

[-] bjorney@lemmy.ca 10 points 2 months ago* (last edited 2 months ago)

It's not necessary but there is no reason not to.

Pros:

production and development programs are more similar
upgrading your base image won't affect your python packages
you can use multi stage builds to create drastically smaller final images

Cons:

you have to type venv/bin/python3 instead of just python3 in the run line of your dockerfile

[-] dwt@feddit.org 3 points 2 months ago

It’s easy to set the path to include the venv in the Dockerfile, that way you never have to activate, either in the run line, nor if you exec into it. Also this makes all your custom entry points super easy to use. Bonus, it’s super easy to use uv to get super fast image builds like that. See this example https://gist.github.com/dwt/6c38a3462487c0a6f71d93a4127d6c73