Kirill Merkushev

@Minion0313 you then trying to reach wrong host - for the selenoid-ui `selenoid-uri` should be `http://selenoid:4444` can you try that? What's the issue with cm? Can I kindly ask you...

Not exactly - selenoid-ui doesn't care about your host. So as stated in docs it should be ``` docker run -d --name selenoid-ui -p 8080:8080 aerokube/selenoid-ui --link selenoid --selenoid-uri http://selenoid:4444...

Just copy as is. `selenoid` is the host name for the container, not for you.

sorry, my bad ``` docker run -d --name selenoid-ui -p 8080:8080 --link selenoid aerokube/selenoid-ui --selenoid-uri http://selenoid:4444 ``` misplaced `link` arg

@Minion0313 please always provide all available logs. Url for your selenoid-ui access wouldn't change.

Ok, lets get back to the beginning. Please kill and remove all containers for selenoid and selenoid-ui then run cm commands as stated in the manual then if it still...

@Minion0313 hey, thx a lot, can you elaborate on how do you know its not linking automatically? Selenoid-ui says its `Up 21 seconds (healthy)` which exactly means everything was linked...

@Minion0313 okay, now I need docker logs for selenoid and selenoid-ui, as well as curl results for the /status endpoint of selenoid (right after you've done with cm)

This could be added here iterating over labels https://github.com/aerokube/selenoid-ui/blob/master/ui/src/components/Sessions/index.js#L93  that would look something like this  needs to be tested with different labels length as well as their number....

@f0rzer I think you want some kind of monitoring - for that better to go for a grafana panel https://github.com/aerokube/selenoid-grafana-example I can understand the timer requirement - that would be...