Re: [Bioc-devel] Docker granularity: containers for individual R packages, running on a normal R installation?

2015-04-15 Thread Dan Tenenbaum
- Original Message - From: Bastian Schiffthaler bast...@bioinformatics.upsc.se To: Martin Morgan mtmor...@fredhutch.org Cc: bioc-devel@r-project.org Sent: Wednesday, April 15, 2015 2:21:08 AM Subject: Re: [Bioc-devel] Docker granularity: containers for individual R packages

Re: [Bioc-devel] Docker granularity: containers for individual R packages, running on a normal R installation?

2015-04-15 Thread Bastian Schiffthaler
maybe starting the docker container in such a way that you have access to your non-docker file system. One way to achieve that is to mount a directory from your host system inside the container: # Creating a subdirectory in /home/rstudio and making it read/write for all (permissions in

Re: [Bioc-devel] Docker granularity: containers for individual R packages, running on a normal R installation?

2015-04-14 Thread Sean Davis
Hi, Wolfgang. One way to think of docker is as a very efficient, self-contained virtual machine. The operative term is self-contained. The docker containers resemble real machines from the inside and the outside. These machines can expose ports and can mount file systems, but something like

Re: [Bioc-devel] Docker granularity: containers for individual R packages, running on a normal R installation?

2015-04-14 Thread Wolfgang Huber
Dear Sean I understand the second point. As for .Call not being the right paradigm, then maybe some other method invocation mechanism? In essence, my question is whether someone already has figured out whether new virtualisation tools can help avoid some of the tradtional Makeovers/configure