-
Notifications
You must be signed in to change notification settings - Fork 522
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
Feature Request: View of which Volumes are being accessed by running containers #2538
Comments
@ucheNkadiCode The relation of Container - volume is Multi-to-multi because volumes can be shared! You can see only Volumes per given container because Volume is the 1st class Docker artifact and can exist without any container that uses it. But you can see orphaned volumes using docker volume ls -qf dangling=true. Volumes are mounted to the given Container paths but don't know the path. Please, clarify what is the exact requirement. Docker volume capabilites. It is recomended to use --label to designate volume usage! |
Just to be clear, without a very significant amount of refactoring work, this cannot be done in the Docker Explorer view. This is due to the many-to-many relationship that @PavelSosin-320 points out. However, there are things we can do--for example, a command like "view attached volumes" that would open a text document listing the volumes, or vice versa. There's also the possibility of making a web view but that would also be a very significant amount of work. |
I suppose the volume labeling and volume view filtered by the label is easy and fulfill 90% of practical requirements. The use of metadata is always practical. |
Consider listing volume mounts under containers with links to the actual volume |
This could be solved by #2592. |
This is now released in Docker extension version 1.10.0. |
When I'm running multiple containers whether it be through a compose group or multiple single Docker projects, I want to have some sort of view for all the volumes that are being accessed on my host machine alongside which containers are accessing them.
The text was updated successfully, but these errors were encountered: