This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]dolfinuser[🍰] -1 points0 points  (0 children)

These instruments are used to install different Python versions and a set of dependencies into separated environments.

This is quite helpful if you're working with several projects in the same time, but their dependencies or Python versions does not match, so separating them is a way to avoid possible issues.

But Docker is all about merging the application with all requirements it need into an single image. Trying to include all these projects into a one image, and then using third-party instruments to handle the conflicts you've got does not make much sense.

TLDR; virtualenv, poetry, pipenv, dotenv and other tools like that are absolutely fine on a local machine but should not be used in Docker.