[lug] Docker

[Bear Giles]

​The image starts quickly, it's the services on the image that may take a
while to come up. Single node Hadoop clusters may take several minutes to
fully launch.​ Ditto appservers (jboss, tomcat) with a fair number of
webapps. The parameter is tunable but 60s is the default.

If you're launching a webservice there's an alternative - the library can
hit a REST call wait for it to come up instead of waiting a blind amount of
time. If it becomes a problem we can probably fork the library and do
something similar with other services, e.g., not return until the library
can establish a JDBC connection instead of waiting for a fixed amount of
time.

On Tue, Jul 24, 2018 at 10:24 AM, Zan Lynx <zlynx at acm.org> wrote:

> On 07/24/2018 06:37 AM, Bear Giles wrote:
> > Maintaining a docker image is much more manageable. Unfortunately
> > there's nearly always a 60s delay to allow time for the server to come
> > up. We need to look into modifying our tests so they can run in
> parallel.)
>
> There's something very wrong in your Docker storage setup. You need to
> be using aufs or btrfs. Some filesystem that does overlays or snapshots.
> 60s sounds like it's doing file copies.
>
> We do a lot of Docker where I work and starting a docker container
> that's already downloaded is *instant*. No noticeable delay at all.
>
> --
>                 Knowledge is Power -- Power Corrupts
>                         Study Hard -- Be Evil
> _______________________________________________
> Web Page:  http://lug.boulder.co.us
> Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
> Join us on IRC: irc.hackingsociety.org port=6667 channel=#hackingsociety
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lug.boulder.co.us/pipermail/lug/attachments/20180724/93b03b3c/attachment.html>