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

Failed to start: Selenoid with registry if dont run docker pull #250

Closed
patsevanton opened this issue Nov 8, 2019 · 4 comments · Fixed by #256
Closed

Failed to start: Selenoid with registry if dont run docker pull #250

patsevanton opened this issue Nov 8, 2019 · 4 comments · Fixed by #256
Labels
Milestone

Comments

@patsevanton
Copy link

Hello!

cm_linux_amd64 selenoid start --browsers android:4.4  --registry https://docker-registry.tools.myteam.ru:10443
> Using Docker
- Your Docker API version is 1.39
> Downloading Selenoid...
- Fetching tags for image aerokube/selenoid
registry.ping url=https://docker-registry.tools.myteam.ru:10443/v2/
registry.tags url=https://docker-registry.tools.myteam.ru:10443/v2/aerokube/selenoid/tags/list repository=aerokube/selenoid
- Pulling image docker-registry.tools.myteam.ru:10443/aerokube/selenoid:1.9.3
> Configuring Selenoid...
> Processing browser "android"...
- Fetching tags for image selenoid/android
registry.tags url=https://docker-registry.tools.myteam.ru:10443/v2/selenoid/android/tags/list repository=selenoid/android
- Pulling image docker-registry.tools.myteam.ru:10443/selenoid/android:4.4
> Pulling video recorder image...
- Pulling image docker-registry.tools.myteam.ru:10443/selenoid/video-recorder:latest-release
> Configuration saved to /root/.aerokube/selenoid/browsers.json
> Starting Selenoid...
x Failed to start: Selenoid image is not downloaded: this is probably a bug
docker inspect selenoid
[]
Error: No such object: selenoid
docker kill -s HUP selenoid
Error response from daemon: Cannot kill container: selenoid: No such container: selenoid
sestatus 
SELinux status:                 disabled
/usr/local/bin/aerokube-cm selenoid start --vnc --force --browsers android:4.4  --registry https://docker-registry.tools.myteam.ru:10443
> Using Docker
- Your Docker API version is 1.39
> Downloading Selenoid...
- Fetching tags for image aerokube/selenoid
registry.ping url=https://docker-registry.tools.myteam.ru:10443/v2/
registry.tags url=https://docker-registry.tools.myteam.ru:10443/v2/aerokube/selenoid/tags/list repository=aerokube/selenoid
- Pulling image docker-registry.tools.myteam.ru:10443/aerokube/selenoid:1.9.3
> Configuring Selenoid...
> Processing browser "android"...
- Fetching tags for image selenoid/android
registry.tags url=https://docker-registry.tools.myteam.ru:10443/v2/selenoid/android/tags/list repository=selenoid/android
- Requested to download VNC images...
- Pulling image docker-registry.tools.myteam.ru:10443/selenoid/vnc_android:4.4
> Pulling video recorder image...
- Pulling image docker-registry.tools.myteam.ru:10443/selenoid/video-recorder:latest-release
> Configuration saved to /root/.aerokube/selenoid/browsers.json
> Starting Selenoid...
x Failed to start: Selenoid image is not downloaded: this is probably a bug
@patsevanton patsevanton changed the title Failed to start: Selenoid image is not downloaded: this is probably a bug Failed to start: Selenoid image is not downloaded: this is probably a bug with registry Nov 8, 2019
@patsevanton
Copy link
Author

patsevanton commented Nov 8, 2019

cm_linux_amd64  selenoid start --force --vnc --last-versions 1 --registry https://docker-registry.tools.myteam.ru:10443
> Using Docker
- Your Docker API version is 1.39
> Downloading Selenoid...
- Fetching tags for image aerokube/selenoid
registry.ping url=https://docker-registry.tools.myteam.ru:10443/v2/
registry.tags url=https://docker-registry.tools.myteam.ru:10443/v2/aerokube/selenoid/tags/list repository=aerokube/selenoid
- Pulling image docker-registry.tools.myteam.ru:10443/aerokube/selenoid:1.9.3
> Configuring Selenoid...
> Processing browser "firefox"...
- Fetching tags for image selenoid/firefox
registry.tags url=https://docker-registry.tools.myteam.ru:10443/v2/selenoid/firefox/tags/list repository=selenoid/firefox
- Requested to download VNC images...
- Pulling image docker-registry.tools.myteam.ru:10443/selenoid/vnc_firefox:70.0
> Processing browser "chrome"...
- Fetching tags for image selenoid/chrome
registry.tags url=https://docker-registry.tools.myteam.ru:10443/v2/selenoid/chrome/tags/list repository=selenoid/chrome
- Requested to download VNC images...
- Pulling image docker-registry.tools.myteam.ru:10443/selenoid/vnc_chrome:78.0
> Processing browser "opera"...
- Fetching tags for image selenoid/opera
registry.tags url=https://docker-registry.tools.myteam.ru:10443/v2/selenoid/opera/tags/list repository=selenoid/opera
- Requested to download VNC images...
- Pulling image docker-registry.tools.myteam.ru:10443/selenoid/vnc_opera:64.0
> Pulling video recorder image...
- Pulling image docker-registry.tools.myteam.ru:10443/selenoid/video-recorder:latest-release
> Configuration saved to /root/.aerokube/selenoid/browsers.json
> Starting Selenoid...
x Failed to start: Selenoid image is not downloaded: this is probably a bug

@patsevanton
Copy link
Author

patsevanton commented Nov 8, 2019

docker pull aerokube/selenoid
Using default tag: latest
latest: Pulling from aerokube/selenoid
c87736221ed0: Already exists 
9c02c43351d6: Pull complete 
28670770ceaf: Pull complete 
Digest: sha256:234aad2a20f6e5bcd5a65b86e773a3d4a55cb76473117420f5be0b5160c8386b
Status: Downloaded newer image for aerokube/selenoid:latest



cm_linux_amd64 selenoid start --force --vnc --last-versions 1 --registry https://docker-registry.tools.myteam.ru:10443
> Using Docker
- Your Docker API version is 1.39
> Downloading Selenoid...
- Fetching tags for image aerokube/selenoid
registry.ping url=https://docker-registry.tools.myteam.ru:10443/v2/
registry.tags url=https://docker-registry.tools.myteam.ru:10443/v2/aerokube/selenoid/tags/list repository=aerokube/selenoid
- Pulling image docker-registry.tools.myteam.ru:10443/aerokube/selenoid:1.9.3
> Configuring Selenoid...
> Processing browser "opera"...
- Fetching tags for image selenoid/opera
registry.tags url=https://docker-registry.tools.myteam.ru:10443/v2/selenoid/opera/tags/list repository=selenoid/opera
- Requested to download VNC images...
- Pulling image docker-registry.tools.myteam.ru:10443/selenoid/vnc_opera:64.0
> Processing browser "firefox"...
- Fetching tags for image selenoid/firefox
registry.tags url=https://docker-registry.tools.myteam.ru:10443/v2/selenoid/firefox/tags/list repository=selenoid/firefox
- Requested to download VNC images...
- Pulling image docker-registry.tools.myteam.ru:10443/selenoid/vnc_firefox:70.0
> Processing browser "chrome"...
- Fetching tags for image selenoid/chrome
registry.tags url=https://docker-registry.tools.myteam.ru:10443/v2/selenoid/chrome/tags/list repository=selenoid/chrome
- Requested to download VNC images...
- Pulling image docker-registry.tools.myteam.ru:10443/selenoid/vnc_chrome:78.0
> Pulling video recorder image...
- Pulling image docker-registry.tools.myteam.ru:10443/selenoid/video-recorder:latest-release
> Configuration saved to /root/.aerokube/selenoid/browsers.json
> Starting Selenoid...
> Successfully started Selenoid

@patsevanton patsevanton changed the title Failed to start: Selenoid image is not downloaded: this is probably a bug with registry Failed to start: Selenoid with registry if dont run docker pull Nov 8, 2019
@vania-pooh vania-pooh added the bug label Nov 8, 2019
@vania-pooh vania-pooh added this to the 1.7.2 milestone Nov 8, 2019
@vania-pooh
Copy link
Member

@patsevanton yes, this seems to be a bug.

@patsevanton
Copy link
Author

May be try download aerokube/selenoid, but download docker-registry.tools.myteam.ru:10443/aerokube/selenoid:1.9.3

After aerokube/selenoid:latest - is ok

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants