And this is the log I get in docker logs

@vaniaPooh do you need more logs ?

need to take a look at browser container logs

@vaniaPooh  @aandryashin
подскажите какую версию DOCKER_API_VERSION нужно указывать при запуске ggr / cm selenoid ?

никакую не нужно, он сам определяет

https://aerokube.com/selenoid/latest/#_recommended_docker_settings  
-это раньше нужно было  ?

да

понял, спасибо!

@vaniaPooh browser container logs stops here :


PS C:\windows\system32> docker logs elated_ritchie
2021/03/22 10:12:35 [INIT] [Listening on :7070]
E: [pulseaudio] client-conf-x11.c: xcb_connection_has_error() returned true
xcb_connection_has_error() returned true
21
Waiting X server...
Waiting X server...
Logging to: /dev/null
Waiting X server...
Waiting X server...
Waiting X server...
Waiting X server...
Waiting X server...
Waiting X server...
Waiting X server...
Waiting X server...
Waiting X server...
Starting ChromeDriver 88.0.4324.27 (6347fe8bf1e48bd0c54d07dc55ca011cf40861c9-refs/branch-heads/4324@{#450}) on port 4444
All remote connections are allowed. Use an allowlist instead!
Please see https://chromedriver.chromium.org/security-considerations for suggestions on keeping ChromeDriver safe.

--- x11vnc loop: 1 ---

ChromeDriver was started successfully.
--- x11vnc loop: waiting for: 105

PORT=5900

everything seems to start... Are you running everything e.g. with docker compose?

Привет!
Подскажите пожалуйста как запустить docker-compose так чтобы мой селеноид localhost:4444 видел приложение развернутое в другом контейнере по localhost: 9001(мне принципиально нужно стучаться именно в localhost, через docker-network все работает но мне не подходит что вместо localhost нужно писать имя контейнера)

@vaniaPooh no. I'm using CM

So I don't know if docker compose is used behind

can you then take a look at system metrics of the server, probably it's just overloaded

with 0 container ?

is it a clean VM or something else is running there?

are you using e.g. CentOS and stuff like SELinux

a clean VM, with only docker

a windows server

could be because on Windows you gave insufficient resources to Docker