govint
commented
7 years ago Setting to spiderman. A typical developer use case would be for a developer to run a container to checkout code, do a sandbox build and publish binaries. The developer creates a non persistent disk of required size and runs the container with that. On container exit the disk is no longer needed and is released.
Docker also has the option to create disks when a container is run, but user has no option to specify the size or any properties of the disk at that time. Plus docker won't delete the volume(s) that it automatically creates when a container is run.
shaominchen
Use cases where a container wants to use a scratch volume to create temporary data, especially one thats cloned from a "base volume" can benefit from a "non-persistent" volume from the vSphere plugin. The volume is created and used (attach/detach) exactly once. The detach deletes the volume. This issue is to add a volume create-time option to specify creating a non-persistent disk thats either stand-alone or cloned from (existing feature) another disk. The volume exists only as long as the first attach and the detach (container exits) should delete the volume.