There does not appear to be a way to clean up volumes created by kitchen-docker about kitchen-docker HOT 4 CLOSED

I've just added support for the --mount option in #363.

EDIT: That said, this issue with volumes being cleaned up could also use a fix. My ruby is barely passable as it is, though.

from kitchen-docker.

If you add run_options: --rm it will remove any anonymous volumes. This does have a few side effects:

• It removes the filesystem after the container stops which can make troubleshooting tougher (fixable by removing it as needed).
• This breaks (results in an error) when you run kitchen destroy. This raises issues though as the kitchen destroy exit code (20) is the same as a failed test run.

All of this being said, this is an issue with docker volumes in general.

from kitchen-docker.

Yeah, this is a byproduct of using the -v argument without a volume name or path. It could theoretically be solved by doing some parsing on the paths in volumes and creating unique volume names which can be cleaned in a later kitchen destroy.

However, according to the docker-run manpage:

See also --mount, which is the successor of --tmpfs and --volume.  Even though
there is no plan to deprecate --volume, usage of --mount is recommended.

Given this, and the fact that my PR to introduce support for the --mount parameter has been merged and is in an official release of kitchen-docker, I wouldn't be opposed to closing this as WONTFIX.

from kitchen-docker.

Closing per the above comment.

from kitchen-docker.