Currently when reprounzip dj record exits, the target directory and the reprounzip_image_xxx image still exist (from reprounzip-docker), and a container is still running (reprounzip_detached_xxx).
Those should probably get cleaned up automatically (I'm fine with a --skip-destoy here, matching --skip-setup)
Currently when
reprounzip dj recordexits, thetargetdirectory and thereprounzip_image_xxximage still exist (from reprounzip-docker), and a container is still running (reprounzip_detached_xxx).Those should probably get cleaned up automatically (I'm fine with a
--skip-destoyhere, matching--skip-setup)