Building the aerokube/selenoid and selenoid/vnc images

[aerokube]

Building the aerokube/selenoid and selenoid/vnc images

[vania-pooh]

@ruescar done.

[timothyjmtan]

I'm sorry, I just read the README.md.

Based on this line:
Building procedure is automated with shell scripts selenium/build-dev.sh and selenium/build.sh that generate Dockerfile and then create browser and driver layers respectively.

Do I thus just need to checkout the entire repository, and just run both build-dev.sh and build.sh with the relevant arguments passed into them?

[vania-pooh]

@timothyjmtan

1. Building Selenoid is described in: https://aerokube.com/selenoid/latest/#_contributing_development
2. Just noticed that README.md in this repo is outdated. Will update today.

[vania-pooh]

@timothyjmtan see https://github.com/aerokube/selenoid-images#how-to-build-images-yourself.

[timothyjmtan]

Many thanks, @vania-pooh , for the new documentation. It is very clear and concise. I'll try it out and let you know.

[timothyjmtan]

Hello @vania-pooh , I did a
$ ./automate_chrome.sh 70.0.3538.67-1 2.43 70.0

And I was stuck here:
Step 1/4 : FROM selenoid/base:4.0
Trying to pull repository registry.access.redhat.com/selenoid/base ...

I'm stuck here because I am unable to connect out into the internet to grab the image. I notice that the folder 'base/base_4' contains the image for selenoid/base:4.0, which is actually using base:3.0, and so on... till base:1.0 is using ubuntu:16.04.

In my case, do I need to manually build all the base layers first in order to get a local version of 'base:4.0' to proceed?

[vania-pooh]

@timothyjmtan yes, just build base/base_4 image.

[ruescar]

@vania-pooh I think it would be nice to add an example on how to build an image locally from the a browser deb package as opposed to use apt to the README file.