Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

selenium/standalone-chrome fails on restart command #257

Closed
go2guy opened this issue Aug 11, 2016 · 2 comments
Closed

selenium/standalone-chrome fails on restart command #257

go2guy opened this issue Aug 11, 2016 · 2 comments

Comments

@go2guy
Copy link

go2guy commented Aug 11, 2016

selenium/standalone-chrome fails on restart command with the following error:
xvfb-run: error: Xvfb failed to start

  1. docker run -d -p 6666:4444 --name Chrome -P selenium/standalone-chrome
  2. docker ps -a results
    CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
    0ff7f108a98f selenium/standalone-chrome "/opt/bin/entry_point" 3 seconds ago Up 2 seconds 0.0.0.0:6666->4444/tcp Chrome

3.. docker restart Chrome
Error Message in log:
xvfb-run: error: Xvfb failed to start

  1. docker ps -a results
    CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
    0ff7f108a98f selenium/standalone-chrome "/opt/bin/entry_point" 37 seconds ago Exited (1) 1 seconds ago Chrome

The restart command works fine for selenium/standalone-chrome-debug.

@gurukiran007
Copy link

#256 Solves it, issue with debug containers only

@go2guy
Copy link
Author

go2guy commented Aug 18, 2016

@gurukiran007 this issue is not with debug containers.

"selenium/standalone-chrome fails on restart command"

@lock lock bot locked and limited conversation to collaborators Aug 14, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants