Does Poetry's default virtualenv location leave production containers without installed dependencies?
A Python service managed with Poetry (assuming the 1.8–2.x configuration model) needs a production image whose runtime interpreter actually contains the packages that poetry install resolves. On a developer workstation this is rarely visible, because the virtualenv is created and activated in place. By documented default, however, Poetry creates virtualenvs