We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
It would be useful to find a way to map an overlayFS ID to the container that actually used it.
e.g. given this path on a server running Docker:
/mnt/docker/var/lib/docker/overlay2/6688ce711806faead06aae3ff534ab21183a087241d3a890741f0c3b437b179c/diff/var/tmp/malware
Find out in which container 6688ce711806faead06aae3ff534ab21183a087241d3a890741f0c3b437b179c is being used.
The text was updated successfully, but these errors were encountered:
Display the working directory hash when listing containers (fix #55) (#…
127506b
…57) * Show working dir * fix tests
Successfully merging a pull request may close this issue.
It would be useful to find a way to map an overlayFS ID to the container that actually used it.
e.g. given this path on a server running Docker:
/mnt/docker/var/lib/docker/overlay2/6688ce711806faead06aae3ff534ab21183a087241d3a890741f0c3b437b179c/diff/var/tmp/malware
Find out in which container 6688ce711806faead06aae3ff534ab21183a087241d3a890741f0c3b437b179c is being used.
The text was updated successfully, but these errors were encountered: