[Container-tools] Including docker images in ADB Vagrant box
Langdon White
langdon at redhat.com
Tue Nov 3 15:28:19 UTC 2015
On 11/03/2015 10:19 AM, Vaclav Pavlin wrote:
>
>
> On Tue, Nov 3, 2015 at 4:00 PM, Lalatendu Mohanty <lmohanty at redhat.com
> <mailto:lmohanty at redhat.com>> wrote:
>
> On 11/03/2015 08:22 PM, Karanbir Singh wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 03/11/15 13:51, Vaclav Pavlin wrote:
>
> On Tue, Nov 3, 2015 at 2:50 PM, Karanbir Singh
> <kbsingh at redhat.com <mailto:kbsingh at redhat.com>
> <mailto:kbsingh at redhat.com <mailto:kbsingh at redhat.com>>>
> wrote:
>
> On 29/10/15 14:27, Vaclav Pavlin wrote:
>
> OTOH if the images are already in the box you can have
> you dev
> env really local once you pull the Vagrant box and
> re-upping your
> box will not require internet connection.
>
> 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.
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.
langdon
[1]: http://fgrehm.viewdocs.io/vagrant-cachier/
> Wont it be a far better solution to just map a local host
> directory
> to docker's storage inside the instance via the
> Vagrantfile ? that
> way a local cache of the backing store exists on a vagrant
> destroy
> and up.
>
>
> Wouldn't that be problematic on Windows?
>
> no more or less than any other persistent storage in windows.
> or are
> you saying that docker is unable to use the shared vol due to
> filesys
> attrib etc ?
>
> No idea, you are right about generality of this problem, though I
> would be a bit more concern with the Docker itself (i.e. the laying)
>
>
> How will you put the docker images on the shared directory/storage?
>
>
> IMO, what KB meant, is to pull them on first vagrant up and keep them
> there for any subsequent destroy && run
>
>
>
> - -- 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)
>
> iQEcBAEBAgAGBQJWOMo1AAoJEI3Oi2Mx7xbtNS4IAMPCHH9RLQAc5V3pmet1DA3y
> hQEi/kNG0wTkH/wgaVvMOfqfUVR89ylSS9edC8xhq6cueZBdLzAvR8cj4aQbI69V
> Qc7vkRcsIhp+S4zrpik2+2KZhPg4JkxVTRMSVq0+3H7UklObxqeJxHy7qlTfvee9
> GCWefnm7uzrpVcuA/HUG8ycilc8pNaw1l0i492x8pPDXxkqYdzOozLZM10uivtXX
> RdTzt6iRQ6+/7gbVCq3kgzxDeO3xp0W9q4vqBBLh74WddbdOLpweOzPzhx8NKV+F
> oimKjQtP1r976f3yZ50SeC5th1VT4o2oNQmkQZ8ZAqDGN3fXsNLov35eQbSKdpk=
> =qbKy
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> Container-tools mailing list
> Container-tools at redhat.com <mailto:Container-tools at redhat.com>
> https://www.redhat.com/mailman/listinfo/container-tools
>
>
> _______________________________________________
> Container-tools mailing list
> Container-tools at redhat.com <mailto:Container-tools at redhat.com>
> https://www.redhat.com/mailman/listinfo/container-tools
>
>
>
>
> --
> Architect - Senior Software Engineer
> Developer Experience
> Brno, Czech Republic
> Phone: +420 739 666 824
>
>
> _______________________________________________
> Container-tools mailing list
> Container-tools at redhat.com
> https://www.redhat.com/mailman/listinfo/container-tools
More information about the Container-tools
mailing list