Closed bonigarcia closed 6 years ago
I just found the solution for my problem. Simply changing the way in which the container is started:
docker run --rm --cap-add=SYS_ADMIN -p 4444:4444 selenoid/vnc:chrome_64.0
Sorry for the noise.
:)
I'm opening this issue again since I have an additional problem. The command before actually works:
docker run --rm --cap-add=SYS_ADMIN -p 4444:4444 selenoid/vnc:chrome_64.0
... but the problem is that I cannot stop the container gracefully. Using Ctrl-C is not working, and using docker stop
gets stalled for a while until it is finally closed.
Any idea? Thanks again!
Selenoid is removing container with --force
flag. Also to use Ctrl-C you have to launch container in interactive mode:
docker run -it ....
Yes, using the --force
flag did the trick, thank you @vania-pooh.
I'm trying to use the Selenoid Docker images for Chrome directly, without using the Selenoid Hub. To that, I simply start a Chrome in Docker with the following command:
docker run --rm -p 4444:4444 selenoid/vnc:chrome_64.0
Then, I have a JUnit 4 test as follows:
Unfortunately it does not work. The container logs are the following:
It continues stalled and I have to stop manually the container. I tried to solve for similar issues but I did not find the solution yet.
Any idea about this?
Thank you very much in advance.