нет,мы это просто удаляли недавно

вы где такое прочитали?

не у вас, поэтому и уточняю, статья довольно свежая была.

в целом это правильная команда, но лучше просто пойти в гитхаб и скачать руками https://github.com/aerokube/cm/releases

сейчас попробую все переподнять ,новым скриптом

нет все равно в упор не видит url

[root@ext-edms-sel-centos aerokube-cm]# ls -l
total 24808
-rwxr-xr-x. 1 root root 12701696 Oct  1 05:54 cm
-rw-r--r--. 1 root root 12701696 Jul  8 06:17 cm_linux_amd64
[root@ext-edms-sel-centos aerokube-cm]#  chmod u+x cm_linux_amd64
[root@ext-edms-sel-centos aerokube-cm]# ./cm_linux_amd64 selenoid start --port 8090 --args "-limit 10"
> Using Docker
- Your Docker API version is 1.40
> Selenoid is already downloaded
> Selenoid is already configured
> Starting Selenoid...
> Successfully started Selenoid
[root@ext-edms-sel-centos aerokube-cm]# ./cm_linux_amd64 selenoid-ui start --port 8091 --args "--selenoid-uri http://172.30.49.62:8090"
> Using Docker
- Your Docker API version is 1.40
> Selenoid UI is already downloaded
> Starting Selenoid UI...
> Successfully started Selenoid UI
[root@ext-edms-sel-centos aerokube-cm]# docker ps
CONTAINER ID        IMAGE                         COMMAND                  CREATED             STATUS                            PORTS                    NAMES
cf71a287569c        aerokube/selenoid-ui:1.10.1   "/selenoid-ui --sele…"   3 seconds ago       Up 2 seconds (health: starting)   0.0.0.0:8091->8080/tcp   selenoid-ui
3ba0be114d6e        aerokube/selenoid:1.10.0      "/usr/bin/selenoid -…"   36 seconds ago      Up 36 seconds                     0.0.0.0:8090->4444/tcp   selenoid

[root@ext-edms-sel-centos aerokube-cm]# docker logs cf71a287569c
2020/10/01 14:40:39 [INIT] [Listening on :8080]
2020/10/01 14:40:39 Client added. 1 registered clients
2020/10/01 14:40:39 Client added. 2 registered clients
2020/10/01 14:40:45 [ERROR] [Can't get status: Get "http://172.30.49.62:8090/status": dial tcp 172.30.49.62:8090: connect: no route to host]

видимо придется в ручную контейнеры поднимать , сейчас пробну еще на тестовой убунте

на убунте дефолтной сразу завелось . Возможно чет не донастроил , все равно спасибо.

Hello everyone, Could anyone help with fetching sessionId from docker container logs? If anyone has a script or command handy. Thank you!

Try it

Thank you.

Everyone, I am running tests on 16 core machine with 46 GB RAM On increasing the parallel execution count beyond 10, I see an increased number of failures due to element not visible exception. But if I disable video recording then I am able to run 20 parallel sessions. Is video recording that CPU intensive (ffmpeg format) or am I missing something?

yes video recording is expensive, and consumes as much cpus as available...

Thank you for the quick response. I saw the recommended limit of parallel containers to be 1.5or 2 * number_of_cores in the documentation. Could you please share is it with or without a video recording?

for video recording you need +1 cpu... please note that we have new project that was developed with efficient resource control in mind, it is called moon and runs in kubernetes and starts browsers with assigned resources, could you please check it:
https://aerokube.com/moon/latest/#_moon_vs_selenoid

oh thank you for the information. That means 20 cpus are being used for 10 parallel tests with video recording enabled. For 16 core, at least 24 parallel session should work. Am I right? Sure, I will look into moon.

you need 1 cpu for browser + 1 cpu for video container, on 16 cores only 8 sessions will work as usual, more parallel sessions can lead to performace degradation.

Thank you very much for the clarification👍

Доброе утро. Подскажите пожалуйста могули я посмотреть количество потребляемых(выделенных) ресурсов одним контейнером. Если могу то как и где ?

докер инспект выделенные , стейт потребляемые

Спасибо