You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 21, 2021. It is now read-only.
Hi,
my docker version is 20.10.4 and working on Linux
successfully pulled both elgalu/selenium and dosel/zalenium images
after executing the command
input : docker run --rm -ti --name zalenium -p 4444:4444 -v /var/run/docker.sock:/var/run/docker.sock -v /tmp/videos:/home/seluser/videos dosel/zalenium start output : Docker binary already present, will use that one.
Docker version 18.09.0, build 4d60db4
-- LOG 13:30:04:270583909 Ensuring docker works...
-- LOG 13:30:04:554602350 Ensuring docker-selenium is available...
haveged: haveged starting up
Copying files for Dashboard...
it was stuck at copying files for dashboard for hours(tried so many times), from that point there is no response or it is not throwing any error and unable to find the cause
and dosel/zalenium container is up and running @elgalu@diemol@hjacobs
The text was updated successfully, but these errors were encountered:
Hi,
my docker version is 20.10.4 and working on Linux
successfully pulled both elgalu/selenium and dosel/zalenium images
after executing the command
input : docker run --rm -ti --name zalenium -p 4444:4444 -v /var/run/docker.sock:/var/run/docker.sock -v /tmp/videos:/home/seluser/videos dosel/zalenium start
output : Docker binary already present, will use that one.
Docker version 18.09.0, build 4d60db4
-- LOG 13:30:04:270583909 Ensuring docker works...
-- LOG 13:30:04:554602350 Ensuring docker-selenium is available...
haveged: haveged starting up
Copying files for Dashboard...
it was stuck at copying files for dashboard for hours(tried so many times), from that point there is no response or it is not throwing any error and unable to find the cause
and dosel/zalenium container is up and running
@elgalu @diemol @hjacobs
The text was updated successfully, but these errors were encountered: