Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Revert to using named volumes #578

Closed
cgardens opened this issue Oct 15, 2020 · 3 comments
Closed

Revert to using named volumes #578

cgardens opened this issue Oct 15, 2020 · 3 comments
Labels
type/enhancement New feature or request

Comments

@cgardens
Copy link
Contributor

Tell us about the problem you're trying to solve

docker-compose pushed an update that has made local volumes unusable on mac (issue: docker/compose#7867). That has forced us to remove the use of local named volumes and instead mount raw directories. This precipcated a bunch of hacks (PR: #576)

Describe the solution you’d like

  • Once docker-compose has addressed this issue, we should bring back local named volumes.
  • We should also get rid of the dependency between *_DOCKER_MOUNT and *_ROOT. Currently if a directory is being mounted, these two env variables need to be set to be the same absolute path.
@cgardens cgardens added the type/enhancement New feature or request label Oct 15, 2020
@cgardens
Copy link
Contributor Author

we have gone ahead and went full to using volumes.

@tom-haines
Copy link

@cgardens re docs/info, issue is still marked as a TODO see .env.dev in v0.50.30 (just fyi)

@joceliovieira
Copy link

any updates?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants