Hacker News Reader

Comment by hiccuphippo | Hacker News Reader

As a workaround you could rename your .env file to something else and mount it as .env in the docker-compose volume options.

View on HN

I'm using autoenv - https://github.com/inishchith/autoenv.

The workaround that I've found for this problem is to set "AUTOENV_ENV_FILENAME=.env.user" and then inside the project folder, I'm now using ".env.user" instead of just ".env".

I'll use this hack until Docker guys fix Docker Compose.

Does this (and the one linked to: https://direnv.net/docs/development.html) do anything that a simple bash entry can't:

  function lenv {
    if [ -f '.env' ]; then
      source .env
    fi
  }
  function cd { builtin cd $@; lenv; }

Depending on how desperately you need to fix this and how hacky you're willing to go, LD_PRELOAD could help here as well. (i.e. https://github.com/randombk/rust-ldpreload-read)

How does this help all the existing applications, tools, scripts etc. that use .env?

If you wanna make it work; this is sadly the only way until Docker Compose is patched.

Rename .env to something else and reconfigure autoenv.

Right. Usually workarounds actually, you know, work :-P

Those applications running inside the container would see .env as the mounted file but Docker-compose would still see the original .env file in the filesystem.

Reply on news.ycombinator.com