Ivan Krutov

@matthewdoerksen not all browsers currently support W3C. I think we could update code snippets for W3C in Selenoid UI.

@vlidu any log entries from Selenoid container would definitely help to diagnose.

@vlidu yeah, this is because you have a Linux binary inside Docker container, whereas you need ARM. Just compile Selenoid from sources with `GOARCH=arm` and build Docker image as shown...

@mjevtovic that's strange because everything is expected to run inside Docker container. However knowing that Docker is reusing host machine kernel - probably `firefox --version` command is causing this issue....

@asemkazi what is your Selenium client version?

@ash0080 thank you for the feedback. Seems to be permissions issue. Either because `selenium` user is not in some `pulseaudio` group or because `pulse` user has no permissions in `/home/selenium`...

@ash0080 will try to build Firefox 59 image with potential fix.

@ash0080 unfortunately can't reproduce this issue. Could you provide an example scenario how to reproduce it?

@ash0080 ok, two parallel requests to the same session. Let me try this.

Could be related to https://github.com/aerokube/selenoid/issues/956.