chrome-headless-trunk | date Headless Chromium right off the trunk | Continuous Deployment library

I am unsure if this is even a good practice, but I am wanting to specify a number of docker images to launch. Ideally it would auto-increment the port and tmp data location.

Here is my current command:

sudo docker run -it -d --restart=always -p=0.0.0.0:9220:9222 -m 1G -v /tmp/chromedata/:/data alpeware/chrome-headless-trunk

Ideally I'd want to be able to spawn, say 5 of these - auto incrementing such as this:

I was trying to figure out how to run headless Chrome in a docker container. Then I have found this. But now I can't figure out how to run my tests in that container.

Can someone give me some a general direction where should I dig, I tried looking through Pupeeteer's docs, yet couldn't find anything. Maybe there's a minimal example in the wild, where I can maybe use Karma or whatever to run tests in a container and log results.

Note though that I would like to compile/bundle javascript outside of the container, and use it just to execute compiled/bundled tests in it.

Maybe later I would like to use the same approach to also run my acceptance tests, but this time by running a web-server outside, possibly in a separate container.

My end goal is to be able to run bunch of test written in Clojurescript, I don't think though anybody has done something like that yet. Maybe somebody has.