Skip to content

Conversation

@Vanuan
Copy link

@Vanuan Vanuan commented Jun 30, 2016

If you specify a volume in Dockerfile, it would be impossible to remove/override it using command line options.
Moreover, it would leave dangling volumes for inexperienced users and users of docker-compose.
In docker-compose, you wouldn't be able to specify mounted volume.
Please let the user specify the volume location.

If you specify a volume in Dockerfile, it would be impossible to remove/override it using options.
Moreover, it would leave dangling volumes for inexperienced users and users of docker-compose.
In docker-compose, you wouldn't be able to specify mounted volume.
Please let the user specify the volume location.
@lgelfan
Copy link

lgelfan commented Jul 19, 2016

If you use your own volume attribute during run or similar, it will use that and not the one in the Dockerfile. At least the one in the Dockerfile keeps it out of the container if someone doesn't specify a volume. I agree that it could/will lead to orphaned volumes but that seems like general issue not specific to this.

@Vanuan
Copy link
Author

Vanuan commented Jul 19, 2016

If you use your own volume attribute during run or similar, it will use that and not the one in the Dockerfile.

If it should, then it is a bug in docker-compose, because for me it doesn't work. There are dangling volumes all over the place.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants