Feature Request: option to disable reading from .env · Issue # 6741 · docker / compose, Hacker News

          

Docker just broke my development environment too. 🙁 As a Python developer I useautoenvextensively so all of my.envfiles start with:

if [ -d "venv" ]; then   deactivate>/ dev / null 2>& 1   source venv / bin / activate fi  export FLASK_APP=service: app ... blah, blah, blach, etc.

This allows me to simplycdinto a folder and have that Python virtual environment immediately activated.

We need a way to disable this behavior or at a minimum have it give a warning and keep going because my.envfile is not meant for docker consumption.