-
-
Notifications
You must be signed in to change notification settings - Fork 428
Launching specs with docker-compose #1019
Comments
I didn't have much luck with xvfb-run so I just put the following into my entrypoint: echo 'Starting Xvfb'
Xvfb :99 -screen 0 1280x1024x24 &
export DISPLAY=:99 (This only runs when we're running |
Could you run something else within |
Well, it seems to be a docker-compose / xvfb problem: |
I'm going to close this issue, as it doesn't seem like a bug in capybara-webkit, but feel free to continue commenting. If you wrap the xvfb-run invocation in a shell, does that have any effect?
I don't know what's causing the hang, but my best guesses are something to do with 1) the default shell 2) stdin 3) interactive vs non-interactive shell invocations. |
Thank you for the courtesy and the reactivity.
I like the 'non-interactive shell' lead, I keep investigating and will keep you informed. |
I'm having the exact same problem. If you find a fix or any more information could you pass it on? |
I endend up writing another Stackoverflow post |
I realize this is an old post, but in case anyone comes across it you should check out the work that Mark Adams did with this handy script. With this script (also take a look at how he uses it in the dockerfiles in that same repo), I'm at least able to run |
I can't launch rspec with docker-compose since I installed capybara-webkit.
This next command just hold up for hours, doing nothing:
$ docker-compose run web xvfb-run -a bundle exec rspec
Running it with the --verbose option don't give much more information.
It's working if I launch a bash terminal in my container and fire the command from there.
$ docker-compose run web bash
then$ xvfb-run -a bundle exec rspec spec
launch the specs correctly.Is there a special config for docker-compose I should be aware of?
The Dockerfile:
I give more details on this Stackoverflow post
The text was updated successfully, but these errors were encountered: