Skip to content
Prev 15254 / 21307 Next

[Bioc-devel] Using BioC vignettes as Jupyter Notebooks

Hi,
On Tue, 2019-07-02 at 09:50 +0000, Martin Morgan wrote:
Hm, the Jupyter can not "talk" to the container that is hosting it, 
so this would have to be done upon startup.
I like that idea to some extend. In particular, 
it'll help not having to carry the BUILD dependencies 
in the container as we currently have in e.g. release_metabolomics2.

A less known feature of Docker is to have two FROM in one Dockerfile, 
e
.g. https://github.com/ProteoWizard/container/blob/master/Dockerfile
where the second FROM can COPY from the above-built container, 
thus dropping any cruft. 

But how would the binary packages then be imported into 
the container ? The volumes work fine on the command line. 
What about a kubernetes cluster ? 

I'd like to suggest to avoid any dependency on the 
filesystem of the host, i.e. no 
-v host-site-library:/usr/local/lib/R/host-site-library

An established way to mount stuff into a container (like bioc-full)
is to use sidecar containers. Basically they share some of their 
filesystem with the "main" container (typical example: 
tomcat main container, sidecar with only the *.war file).

A challenge is duplication. If each binary with required /site-lib/content 
carries Biobase, we'd have 1750 copies of that. This would be solved if we can mount 
the required subset (=dependencies) of the 1750 binaries into site/lib/PACKAGE

Yours,
Steffen