[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [gwl-devel] support for containers
From: |
Ricardo Wurmus |
Subject: |
Re: [gwl-devel] support for containers |
Date: |
Tue, 29 Jan 2019 12:46:25 +0100 |
User-agent: |
mu4e 1.0; emacs 26.1 |
zimoun <address@hidden> writes:
>> Some thoughts on how the data store should work: it’s easy to add stuff
>> to the store (we just hash the inputs leading up to the output,
>> excluding the output itself); but how do we make store items available
>> to a process? When using containers we can bind mount the file to the
>> declared input location; when not using containers we need to link or
>> copy the file from
>
> By store, do you the Guix store? or another store? as GWL store?
A GWL-specific data store. We don’t reuse the Guix store.
> By inputs, do you mean data-inputs and package-inputs?
Data inputs only.
>> I also want to have finer control over inputs. Only declared input
>> *files* should be available in the container, not whole *directories*.
>
> Hum? I make sense.
> Especially for references used by aligners.
> Even if the size of the container will significantly growth. :-)
If users need directories they should declare directories as inputs /
outputs.
--
Ricardo
- [gwl-devel] support for containers, Ricardo Wurmus, 2019/01/28
- Re: [gwl-devel] support for containers, Ricardo Wurmus, 2019/01/29
- Re: [gwl-devel] support for containers, zimoun, 2019/01/29
- Re: [gwl-devel] support for containers,
Ricardo Wurmus <=
- Re: [gwl-devel] support for containers, zimoun, 2019/01/29
- Re: [gwl-devel] support for containers, Ricardo Wurmus, 2019/01/30
- Re: [gwl-devel] support for containers, zimoun, 2019/01/29
- Re: [gwl-devel] support for containers, Ricardo Wurmus, 2019/01/29
- Re: [gwl-devel] support for containers, zimoun, 2019/01/30
- Re: [gwl-devel] support for containers, Ricardo Wurmus, 2019/01/30
Re: [gwl-devel] support for containers, zimoun, 2019/01/29