[Can't get status: Get "http://selenoid:4444/status": context deadline exceeded]

[VinothMessi]

It was working perfectly few days back, suddenly started receiving the above error

[VinothMessi]

My docker-compose:

browsers.json:

[vania-pooh]

@VinothMessi your container name is not selenoid, so --selenoid-uri should use correct value.

[VinothMessi]

Just took it from Selenoid official website:

[VinothMessi]

Its shows like this in the UI:

[vania-pooh]

@VinothMessi your container name is different than selenoid. Sometimes just restarting Docker helps.

[VinothMessi]

I even matched the container name, restarted docker... everything i have tried. Just last week it was working perfectly

[vania-pooh]

@VinothMessi please don't use aerokube/selenoid-ui:latest image. Replace with aerokube/selenoid-ui:1.10.3 or aerokube/selenoid-ui:latest-release (latest release).

[VinothMessi]

I tried it all, the issue remains the same. Am following whatever is given in Selenoid website, but its not working

But am sure it happening only recently, everything was working just days before

[vania-pooh]

@VinothMessi could be also caused by Docker update. We previously seen such issues in some Docker releases.

[VinothMessi]

AH... just updated my docker recently, so how to overcome it?

[vania-pooh]

@VinothMessi either downgrade or wait for the new release. Probably switching to edge Docker version could help.

[VinothMessi]

I updated to the new docker release and the same issue is persisting :(

Any way to over come it? tried everything that was mentioned :(

[VinothMessi]

Docker-compose file to start the selenoid service:

Then run the selenoid-ui container from terminal:
docker run -d --name selenoid-ui --link selenoid -p 8090:8080 aerokube/selenoid-ui:latest-release --selenoid-uri=http://selenoid:4444

Then it works perfectly fine

only when i put together inside compose file issue comes up

Tried everything, so only when trying from compose this issue is there

[aandryashin]

Docker compose runs containers in custom network, you have to give name that network and tell selenoid to start browsers in that network by passing -container-network option. чт, 2 сент. 2021 г., 14:10 Vinoth M ***@***.***>:

…

Docker-compose file to start the selenoid service: [image: image] <https://user-images.githubusercontent.com/34208574/131833249-491145c1-3c84-4aec-b284-4e03b4abe618.png> Then run the selenoid-ui container from terminal: *docker run -d --name selenoid-ui --link selenoid -p 8090:8080 aerokube/selenoid-ui:latest-release --selenoid-uri=http://selenoid:4444 <http://selenoid:4444>* Then it works perfectly fine only when i put together inside compose file issue comes up Tried everything, so only when trying from compose this issue is there — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#1135 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAKY23L44C2VQJQX5WSHYDTT75LTZANCNFSM5CRV4PWA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[VinothMessi]

Tried that also, created a network named Selenoid and linked both the Selenoid containers to it

Still no use

[kim-andrew-v]

I had different issue with connection between selenoid and selenoid-ui

I found that in my docker desktop settings
checkbox "Use Docker Compose V2 release candidate" was enabled

When i disabled it everything went smooth as before. I hope it'll help.

[VinothMessi]

Its already disabled for me :(

Which version of docker you using? am using the latest one : Docker version 20.10.8, build 3967b7d (updated it yesterday)

[kim-andrew-v]

➜ ~ docker --version
Docker version 20.10.8, build 3967b7d
➜ ~ docker-compose --version
docker-compose version 1.29.2, build 5becea4c

[VinothMessi]

Can you share me your compose file?

this is what am using:

[kim-andrew-v]

Sure thing

[VinothMessi]

Found what was causing the issue, in the command i had "-video-recorder-image", "selenoid/video-recorder:7.1"
once i removed it is working file

Sorry, just a question in you compose you have a

volumes:
allure-results:
local: driver

you never used it : may i know the purpose? ad how to map the absolute path?

[jimbalatero]

I had different issue with connection between selenoid and selenoid-ui

I found that in my docker desktop settings
checkbox "Use Docker Compose V2 release candidate" was enabled

When i disabled it everything went smooth as before. I hope it'll help.

This worked for me as well. Thanks

[Amraneze]

I have the same issue. Here is my docker compose file

version: "3"
services:
  selenoid:
    image: "aerokube/selenoid:latest-release"
    container_name: selenoid
    ports:
      - "4444:4444"
    network_mode: bridge
    volumes:
      - "./selenoid:/etc/selenoid"
      - "./selenoid-outputs/output/:/output"
      - "/var/run/docker.sock:/var/run/docker.sock"
      - "./selenoid-outputs/video:/opt/selenoid/video"
      - "./selenoid-outputs/logs:/opt/selenoid/logs"
    environment:
      - "OVERRIDE_VIDEO_OUTPUT_DIR=$PWD/selenoid-outputs/video"
    command: [
        "-conf",
        "/etc/selenoid/browsers.json",
        "-video-output-dir",
        "/opt/selenoid/video",
        "-log-output-dir",
        "/opt/selenoid/logs",
        "-limit",
        "5",
        "-save-all-logs",
        "-enable-file-upload",
      ]

  selenoid-video-recorder:
    image: selenoid/video-recorder:latest-release

  selenoid-ui:
    image: "aerokube/selenoid-ui:latest-release"
    container_name: selenoid-ui
    links:
      - selenoid
    ports:
      - "8080:8080"
    network_mode: bridge
    command: ["--selenoid-uri", "http://selenoid:4444"]

When I ran the command docker compose up I get this error [Can't get status: Get "http://selenoid:4444/status"]

Here are docker & docker compose versions:

When I run docker compose with a new network it works but chrome can't access to my angular project. I'm getting

[vania-pooh]

@Amraneze you can use aliases like docker.for.win.localhost or docker.for.mac.localhost to access host machine services.

[Amraneze]

@Amraneze you can use aliases like docker.for.win.localhost or docker.for.mac.localhost to access host machine services.

It didn't help. I got cannot resolve host

[vania-pooh]

@Amraneze one more candidate is host.docker.internal.

[tnypxl]

I am having this same issue and none of the above steps help.

[lorsatti]

I had the same issue today, using a newly reimaged VM. Only thing that helped for me was moving from docker-compose v2 to the latest docker-compose v1. After that I noticed that the starting order is different in v2, so probably it could be a bug.

UPDATE: After that, I saw this fix. So it would probably work again with v2.6.1. I didn't try it, though.

[Oleborn]

Была такая ошибка - selenoid Can't get status: context deadline exceeded
помогло добавление в selenoid-ui
links:
- selenoid

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.