Include chrome-driver in our docker image

[alaxalves]

Why installing Chrome Driver in our container every Travis build time, when we could just include this in the Dockerfile, generate a docker a Docker image and shorten our Travis build time duration.

I'd like to do the same work here that I have suggested in the following:
publiclab/mapknitter#604
publiclab/mapknitter#598

[welcome]

Thanks for opening your first issue! This space is protected by our Code of Conduct - and we're here to help.
Please follow the issue template to help us help you 👍🎉😄
If you have screenshots or a gif to share demonstrating the issue, that's really helpful! 📸
Do join our Gitter channel for some brainstorming discussions.

[jywarren]

Would this improve the time it currently is taking to download and install chrome? This seems to be breaking our builds a lot and driving build time to 18-24 minutes... pretty wild! But the system tests themselves aren't accounting for the extra time; it seems to be in downloading and building Chrome. I'd love a PR for this if it's related! This is a pretty critical issue for plots2 right now. But even if not related, this sounds cool! Thanks!

…

On Wed, May 15, 2019 at 9:29 AM Álax de Carvalho Alves < ***@***.***> wrote: Why installing Chrome Driver in our container every Travis build time, when we could just include this in the Dockerfile, generate a docker a Docker image and shorten our Travis build time duration. I'd like to do the same work here that I have suggested in the following: publiclab/mapknitter#604 <publiclab/mapknitter#604> publiclab/mapknitter#598 <publiclab/mapknitter#598> — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#5725?email_source=notifications&email_token=AAAF6J5FKBMZ4NACAEV5DCTPVQFYZA5CNFSM4HNDKAU2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4GT5TQEA>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAAF6J32CLACKUVYZWOIE6TPVQFYZANCNFSM4HNDKAUQ> .

[alaxalves]

Would this improve the time it currently is taking to download and install chrome? This seems to be breaking our builds a lot and driving build time to 18-24 minutes... pretty wild! But the system tests themselves aren't accounting for the extra time; it seems to be in downloading and building Chrome. I'd love a PR for this if it's related! This is a pretty critical issue for plots2 right now. But even if not related, this sounds cool! Thanks!
…
On Wed, May 15, 2019 at 9:29 AM Álax de Carvalho Alves < @.***> wrote: Why installing Chrome Driver in our container every Travis build time, when we could just include this in the Dockerfile, generate a docker a Docker image and shorten our Travis build time duration. I'd like to do the same work here that I have suggested in the following: publiclab/mapknitter#604 <publiclab/mapknitter#604> publiclab/mapknitter#598 <publiclab/mapknitter#598> — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#5725?email_source=notifications&email_token=AAAF6J5FKBMZ4NACAEV5DCTPVQFYZA5CNFSM4HNDKAU2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4GT5TQEA>, or mute the thread https://github.com/notifications/unsubscribe-auth/AAAF6J32CLACKUVYZWOIE6TPVQFYZANCNFSM4HNDKAUQ .

Actually it would reduce the time a lot, because everytime the build downloads chrome-drive. And with this we could make the driver already available in our docker image. Another thing that would reduce is do what I have suggested in publiclab/mapknitter#604. The build time would be shortened to something like a docker pull command duration.

[alaxalves]

After we close publiclab/mapknitter#604 we could get into this.