[Container-tools] Including docker images in ADB Vagrant box

[Karanbir Singh]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 03/11/15 15:28, Langdon White wrote:
> but the size of the vagrant box will go up dramatically, and if the
> only way to ship the updates is via box updates, it might be a case
> of just having transferred the problem from one place to another.
> 
> 
>> I agree, this will make the box quite a bit larger, but,
>> personally, I think it is worth it.

the basic assumption we are making here then is that folks dont
already have a workflow thats productive for them, ( ie, the primary
target is people dont dont already use containers and dont already use
vagrant ) - for people already consuming these things, if they have
workflow issues, I think its safe to assume they are willing to find a
broader solution.

be it a case of shipping a docker-registry-in-a-box to complement the
adb box, or finding a local caching solution that people can opt into.

> 
>> I also do not think that we would only update via box updates,
>> this is just a bootstrap. You could still "docker pull" latest.
>> Obviously, we would *also* do box updates but not as the only way
>> to update.
> 
>> I would really like to see us ship a "caching server" of some
>> sort e.g. repofunnel or pulp. However, I don't think those are
>> ready yet for this. We could investigate adding docker support to
>> vagrant-cachier[1]. They are looking for help anyway, but I am
>> not sure how much work that would be.

vagrant-cachier seems to be mostly 3 to 5 lines per cache type, its
just aliasing the existing cache locations to a system shared folder (
eg. /var/cache/yum is kept on a host shared filesystem ). If the
intention is to go down the route of a docker load <payload>, that
shouldn't be too much work ( but someone should estimate it ).

Having said that, a caching solution should not include e a docker
load at all, since this breaks any container metadata and tracking of
either content inside or outside (eg. environment stuff ), and it
pretty solidly breaks the ability to validate anything.

w.r.t the windows question, most vagrant box's there seem to use nfs
for the share which is going to create issues for docker-storage, but
if the intention is to docker load <img>, that should work from a
cache hosted on the shared dir.

regards,

- -- 
Karanbir Singh, The CentOS Project, London, UK
RH Ext. 8274455 | DID: 0044 207 009 4455
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iQEcBAEBAgAGBQJWOeZPAAoJEI3Oi2Mx7xbtZ5QH/02YS6p/dX2KJwTtleT50WvA
j8nJrBrqzhfXOa+hDpaa8M2689sqf31znrLDnAG7LTmGR+Idujnu+gNiM8/Xzzkb
qayNuU5I5XeTl6nmDwyVqFwbpxOk35HPhsjl7aLw/VsH5x0Ezf94s+TjqZw2VDvP
/ABtVzQOkW7vJPjOJjDgWUgvP+m53NITufrhpsFGNbxTfb688m8pCIIMzlYvlzWj
QPINnCEVl+EYm0NIIw0EjqWbc8MkRIrLPNWa5WZtSI/LpFiBfeDz1+9F71eEWMT+
hmSs8h4UWVRV9918mj2Em9IJbN3diowD0We4YMJ7l/S+7pBLR6uDudgTlpyWAag=
=JTnA
-----END PGP SIGNATURE-----