From: Kyle Meyer <kyle@kyleam.com>
To: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
Cc: gwl-devel@gnu.org
Subject: Re: Next steps for the GWL
Date: Thu, 06 Jun 2019 11:07:55 -0400 [thread overview]
Message-ID: <87o93apx9w.fsf@kyleam.com> (raw)
In-Reply-To: <87v9xjja6b.fsf@mdc-berlin.de>
Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de> writes:
>> One of the things I'd love to do
>> with GWL is to make it play well with git-annex, something that would
>> almost certainly be too specific for GWL itself.
[...]
> I wonder what the protocol should look like. Should a workflow
> explicitly request a “git annex” file or should it be up to the person
> running the workflow, i.e. when “git annex” has been configured to be
> the cache backend it would simply look up the declared input/output
> files there.
The latter is what I had in mind. One benefit I see of leaving it up to
the configured backend is that it makes it easier to share a workflow
with someone that doesn't have/want the requirements for a particular
backend.
>>> * add support for executing processes in isolated environments
>>> (containers) — this requires a better understanding of process inputs.
[...]
> This means that it can map file systems into the container and then run
> the process expression in that environment.
>
> One thing I’m not happy about is that I can only mount directories, and
> not individual files that have been declared as inputs. I’d like to
> have more fine-grained access.
Right, limiting to the declared files makes sense.
With `docker run', you can give files to -v:
% ls /tmp/ | wc -l
121
% file /tmp/scratch
/tmp/scratch: ASCII text
% docker run -it --rm -v /tmp/scratch:/tmp/scratch busybox ls /tmp
scratch
It looks like using files works for `guix environment' too, which makes
me think that call-with-container can handle receiving files in MOUNT.
% guix environment -C --ad-hoc coreutils -- ls /tmp | wc -l
0
% guix environment -C --expose=/tmp/scratch=/tmp/scratch --ad-hoc coreutils -- ls /tmp
scratch
next prev parent reply other threads:[~2019-06-06 15:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-29 13:47 Next steps for the GWL Ricardo Wurmus
2019-06-03 15:16 ` zimoun
2019-06-03 16:18 ` Ricardo Wurmus
2019-06-06 11:07 ` zimoun
2019-06-06 12:19 ` Ricardo Wurmus
2019-06-06 13:23 ` Pjotr Prins
2019-06-06 3:19 ` Kyle Meyer
2019-06-06 10:11 ` Ricardo Wurmus
2019-06-06 10:55 ` zimoun
2019-06-06 11:59 ` Ricardo Wurmus
2019-06-06 13:44 ` Pjotr Prins
2019-06-06 14:06 ` Pjotr Prins
2019-06-06 15:07 ` Kyle Meyer [this message]
2019-06-06 20:29 ` Ricardo Wurmus
2019-06-07 4:11 ` Kyle Meyer
2019-06-12 9:46 ` Ricardo Wurmus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.guixwl.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87o93apx9w.fsf@kyleam.com \
--to=kyle@kyleam.com \
--cc=gwl-devel@gnu.org \
--cc=ricardo.wurmus@mdc-berlin.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).