Setup an automatic bind-mount during container creation to allow for easy access to the data
haysberg opened this issue · comments
Reseachers often use rsync to save the data they got from their experiment. By providing a bind-mount somewhere on the host machine, we allow them to easily retrieve the fruit of their efforts.
following-up on this one:
I was mostly thinking aloud when I mentioned this yesterday
We need to think about it twice, because the location where that bind-mounted volume would sit is in the host
But at the same time that host is at constant risk of being erased by the next slice
So that means that data collection must be performed right after the experiment has run - just like in the current rhubarbe-based scenario
And for that reason we might just as well decide that the feature is not worth it altogether
So no hurry at all to implement that one...
hth -- Thierry
Actually I think it shouldn't be too hard to implement that. Simply adding the command at the end of the deploy call should be enough.
Maybe we could bind it to something like /container_fs ?
yes it's simple, but not needed at all, so we should just ditch it for now
Simply added the following arguments to the docker run command :
-v /home/container/container_fs:/var
This should do the job pretty well for now.