Skip to content

Conversation

@Quintasan
Copy link

Proposed changes

Adjust spec for the .env file to adopt the de facto behaviour up until docker/compose@0612d97 was merged.

Some users depended on lines starting with export being ignored by docker-compose so they could use the .env file via source command or some other tools that also read the .env file.

The spec didn't say what would happen with lines not conforming to the syntax. Breakage ensured when the aforementioned merge request was pulled into docker-compose (docker/compose#6511 docker/compose#6838).

There is a feature request for a switch that would prevent docker-compose from reading .env but it only solves the problem of I don't want docker-compose to use my .env file at all (docker/compose#6741). It's implemented in docker/compose#6850

Related issues (optional)

docker/compose#6511
docker/compose#6838

docker/compose#6741
docker/compose#6850

@GordonTheTurtle
Copy link

Deploy preview for docsdocker ready!

Built with commit 6ea3669

https://deploy-preview-9467--docsdocker.netlify.com

@traci-morrison traci-morrison added the area/compose Relates to docker-compose.yml spec or docker-compose binary label Nov 27, 2019
@ulyssessouza
Copy link
Contributor

Hello @Quintasan .

I'm closing this issue, since the behaviour is that lines with export are also taken.
Tested in Docker Compose V1 and V2.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/compose Relates to docker-compose.yml spec or docker-compose binary

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants