Skip to content
This repository was archived by the owner on Dec 17, 2024. It is now read-only.

selenoid/video-recorder images are not fetched from given docker registry #301

Closed
lorsatti opened this issue Jul 27, 2021 · 4 comments
Closed
Labels
Milestone

Comments

@lorsatti
Copy link

Binary
https://github.com/aerokube/cm/releases/download/1.8.0/cm_linux_amd64

How to reproduce:
./cm selenoid start --vnc --registry https://my-registry.example.com
Start session with video support enableVideo: true

Expected
Session starts normally.

Instead
Getting error: start video container: create video container: Error response from daemon: No such image: selenoid/video-recorder:latest-release

Workaround
docker tag my-registry.example.com/selenoid/video-recorder:latest-release selenoid/video-recorder:latest-release

Browser images are fetched correctly from the given docker repository.

@vania-pooh
Copy link
Member

vania-pooh commented Jul 27, 2021

@lorsatti need detailed cm log where video recorder image is being fetched.

@lorsatti
Copy link
Author

sure.
request:

curl -X POST 'http://my-selenoid.host:4444/wd/hub/session' -d '{ 
            "desiredCapabilities":{
                "browserName":"chrome",
                "browserVersion": "91.0",
                "platformName":"ANY",
                "selenoid:options": {
                    "enableVNC": true,
                    "enableVideo": true,
                    "name": "this.test.is.launched.by.curl",
                    "sessionTimeout": "12s" 
                }
            }
        }'

docker logs -f selenoid on selenoid host:

2021/07/27 15:31:13 [-] [NEW_REQUEST] [unknown] [REDACTED]
2021/07/27 15:31:13 [-] [NEW_REQUEST_ACCEPTED] [unknown] [REDACTED]
2021/07/27 15:31:13 [211] [LOCATING_SERVICE] [chrome] [91.0]
2021/07/27 15:31:13 [211] [USING_DOCKER] [chrome] [91.0]
2021/07/27 15:31:13 [211] [CREATING_CONTAINER] [my-registry.example.com/selenoid/chrome:91.0]
2021/07/27 15:31:13 [211] [STARTING_CONTAINER] [my-registry.example.com/selenoid/chrome:91.0] [94a2852ad05e2b4b5c7b8975f94f6f7270795e43a9fb4039495598131e34333d]
2021/07/27 15:31:14 [211] [CONTAINER_STARTED] [my-registry.example.com/selenoid/chrome:91.0] [94a2852ad05e2b4b5c7b8975f94f6f7270795e43a9fb4039495598131e34333d] [0.30s]
2021/07/27 15:31:14 [211] [CREATING_VIDEO_CONTAINER] [selenoid/video-recorder:latest-release]
2021/07/27 15:31:14 [211] [REMOVING_CONTAINER] [94a2852ad05e2b4b5c7b8975f94f6f7270795e43a9fb4039495598131e34333d]
2021/07/27 15:31:14 [211] [CONTAINER_REMOVED] [94a2852ad05e2b4b5c7b8975f94f6f7270795e43a9fb4039495598131e34333d]
2021/07/27 15:31:14 [211] [SERVICE_STARTUP_FAILED] [start video container: create video container: Error response from daemon: No such image: selenoid/video-recorder:latest-release]

@vania-pooh
Copy link
Member

@lorsatti need cm command log. This is selenoid log.

@lorsatti
Copy link
Author

ah ok, the console log when starting with a fresh environment cm selenoid start -r https://my-registry.example.com is

> Using Docker
- Your Docker API version is 1.41
> Selenoid is already downloaded
> Configuring Selenoid...
> Processing browser "firefox"...
- Fetching tags for image selenoid/firefox
registry.ping url=https://my-registry.example.com/v2/
registry.tags url=https://my-registry.example.com/v2/selenoid/firefox/tags/list repository=selenoid/firefox
- Pulling image my-registry.example.com/selenoid/firefox:90.0
- Pulling image my-registry.example.com/selenoid/firefox:89.0
> Processing browser "chrome"...
- Fetching tags for image selenoid/chrome
registry.tags url=https://my-registry.example.com/v2/selenoid/chrome/tags/list repository=selenoid/chrome
- Pulling image my-registry.example.com/selenoid/chrome:92.0
- Pulling image my-registry.example.com/selenoid/chrome:91.0
> Processing browser "opera"...
- Fetching tags for image selenoid/opera
registry.tags url=https://my-registry.example.com/v2/selenoid/opera/tags/list repository=selenoid/opera
- Pulling image my-registry.example.com/selenoid/opera:77.0
- Pulling image my-registry.example.com/selenoid/opera:76.0
> Pulling video recorder image...
- Pulling image my-registry.example.com/selenoid/video-recorder:latest-release
> Configuration saved to /root/.aerokube/selenoid/browsers.json
> Starting Selenoid...
> Successfully started Selenoid

Every subsequent launch outputs:

> Using Docker
- Your Docker API version is 1.41
> Selenoid is already downloaded
> Selenoid is already configured
> Starting Selenoid...
> Successfully started Selenoid

@vania-pooh vania-pooh added the bug label Jul 29, 2021
@vania-pooh vania-pooh modified the milestones: 1.8.1, 1.8.2 Jul 29, 2021
vania-pooh added a commit that referenced this issue Jul 29, 2021
Correct video recorder image for custom Docker registry (fixes #301)
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants