VNC recorder for selenium container creates empty video files

[glebsts]

Hello. Tried selenium example test with chrome recording. No networks and links, just this standard "open wikipedia" behavior. Produces 144 bytes long empty broken video files. Container log reports connection problem. Linux. Containers 1.4.2. Webdriver 3.4.0
I was told in slack it is some kind of known issue, but can't find it here.

Any info? Thnx.

[rnorth]

Sorry, that's odd, I've not seen that before. Are you using Docker networks in any way (either via the Network class or via docker-compose)?

[glebsts]

As I wrote, I have this on default example which does not have network and compose. And I tried that example because ig did not work for me in network.

[earroyoron]

Hi, I'm having same issue. My setup is basic example but, I'm using Mac

The running is OK, only the video is an 13 bytes invalid one...

recording-20171203-192135.flv.zip

My installation

High Sierra 10.13.1
Docker Version 17.09.0-ce-mac35 (19611) Channel: stable a98b7c1b7c

Using

    <dependency>
      <groupId>org.testcontainers</groupId>
      <artifactId>selenium</artifactId>
      <version>1.4.3</version>
      <scope>test</scope>
    </dependency>

The execution

19:21:25.964 [main] INFO  org.testcontainers.dockerclient.UnixSocketClientProviderStrategy - Accessing docker with local Unix socket
19:21:25.966 [main] INFO  org.testcontainers.dockerclient.DockerClientProviderStrategy - Found Docker environment with local Unix socket (unix:///var/run/docker.sock)
19:21:25.970 [main] INFO  org.testcontainers.DockerClientFactory - Docker host IP address is localhost
19:21:26.208 [main] INFO  org.testcontainers.DockerClientFactory - Connected to docker: 
  Server Version: 17.09.0-ce
  API Version: 1.32
  Operating System: Alpine Linux v3.5
  Total Memory: 1998 MB
        �[37;1mℹ︎ Checking the system... �[m
        �[32m✔ Docker version should be at least 1.6.0 �[m
        �[32m✔ Docker environment should have more than 2GB free disk space �[m
        �[32m✔ File should be mountable �[m
        �[32m✔ A port exposed by a docker container should be accessible �[m
19:21:28.884 [main] INFO  org.testcontainers.containers.SeleniumUtils - Selenium API version 2.45.0 detected on classpath
19:21:28.892 [main] INFO  🐳 [selenium/standalone-chrome-debug:2.45.0] - Creating container for image: selenium/standalone-chrome-debug:2.45.0
19:21:29.219 [main] INFO  🐳 [selenium/standalone-chrome-debug:2.45.0] - Starting container with ID: 48bfc5a191b3713fa30026a72ec25ae61b50ac63532a8f8d826341537541407c
19:21:29.823 [main] INFO  🐳 [selenium/standalone-chrome-debug:2.45.0] - Container selenium/standalone-chrome-debug:2.45.0 is starting: 48bfc5a191b3713fa30026a72ec25ae61b50ac63532a8f8d826341537541407c
19:21:30.132 [main] INFO  🐳 [selenium/standalone-chrome-debug:2.45.0] - Container selenium/standalone-chrome-debug:2.45.0 started
19:21:30.137 [main] INFO  🐳 [richnorth/vnc-recorder:latest] - Creating container for image: richnorth/vnc-recorder:latest
19:21:30.465 [main] INFO  🐳 [richnorth/vnc-recorder:latest] - Starting container with ID: 9e73ab33b8d2fa7a52aa1297a7d0037e99466d19c4d9c7653fe9a96d577b555c
19:21:31.021 [main] INFO  🐳 [richnorth/vnc-recorder:latest] - Container richnorth/vnc-recorder:latest is starting: 9e73ab33b8d2fa7a52aa1297a7d0037e99466d19c4d9c7653fe9a96d577b555c
19:21:31.031 [main] INFO  🐳 [richnorth/vnc-recorder:latest] - Container richnorth/vnc-recorder:latest started
        �[32m✔ The word 'meme' is found on a page about rickrolling �[m
19:21:35.146 [main] INFO  org.testcontainers.containers.BrowserWebDriverContainer - Screen recordings for test simplePlainSeleniumTest(SeleniumContainerTest) will be stored at: ./target/recording-20171203-192135.flv

[iirekm]

I have the same, it seems that there's a race condition and replacing 3 in BrowserWebDriverContainer in line:

VncRecordingSidekickContainer recordingSidekickContainer = new VncRecordingSidekickContainer<>(this).withStartupAttempts(3)

with 10 seems to fix this problem.

[rnorth]

I hope that #504 will fix this - sorry that it's taken a while. We'll try and release this coming weekend.