Hosts or guests?
Using VirtualBox implies that your docker application would be running within a
Linux guest.
- Rom
From: Marius Millea [mailto:mmil...@ucdavis.edu]
Sent: Thursday, June 25, 2015 4:10 PM
To: Rom Walton r...@romwnet.org
Cc: boinc_dev@ssl.berkeley.edu
Subject: Re: [boinc_dev]
Yea sorry ambiguous what I meant by host there. The idea is that BOINC
clients are running VBoxwrapper which loads up boot2docker inside of which
I run my Docker apps.
Marius
On Thu, Jun 25, 2015 at 1:38 PM, Rom Walton r...@romwnet.org wrote:
Hosts or guests?
Using VirtualBox implies that
The easiest way is to not tell BOINC about the file -
just create it in the project directory,
and look for it there in subsequent jobs.
The app can get the project dir from the APP_INIT_DATA:
http://boinc.berkeley.edu/trac/wiki/StatusApi
-- David
On 25-Jun-2015 2:10 AM, Marius Millea wrote:
(sorry if this screws up the threading, I can't figure out how to reply to
a specific message given I receive only the digest?)
I see, that makes a lot of sense, thanks. I suppose a followup problem is
that this is a VBox app, which AFAIK only gets access to the mounted
shared/ folder. Is there
I can add another shared directory that points to a scratch area in the
project's directory.
Would that work for you?
- Rom
-Original Message-
From: boinc_dev [mailto:boinc_dev-boun...@ssl.berkeley.edu] On Behalf Of Marius
Millea
Sent: Thursday, June 25, 2015 2:27 PM
To:
Well, that is an interesting.
Ultimately I think there will need to be a fork of vboxwrapper that knows how
to handle the docker daemon as well as VirtualBox.
A 27MB boot image is pretty enticing.
- Rom
From: Marius Millea [mailto:mmil...@ucdavis.edu]
Sent: Thursday, June 25, 2015 4:43 PM
Thanks for the interest. Thus far just Linux, although a Windows machine is
waiting once any of this kind of works. The way I currently envisage it
(which could well change), there would be no forking vboxwrapper required.
Basically I modified the boot2docker ISO to act as multi purpose app (in
Suppose the result of a computation yields a large file which I would like
1) to remain on host
2) to be used in subsequent computations
3) to not be uploaded
I think I know how to do 1), if I have the file in the output template I
can add the copy_file flag. Is there actually any way to do 2 or
