vnc-recorder is not able to write recordings Linux permissions?

[kwbr]

I always get errors, that the recording can not be moved to the target destination. The reason is, that the file to be moved does not exists. The screen.flv is not created. I use Linux as my build server, under MacOS it works.

Could not move recording file from .tmp-volume-1513089992384/screen.flv to target/FAILED-SeleniumContainerTest-simplePlainSeleniumTest-20171212-154641.flv

Wild guess: I read about permission problems writing to the host filesystem under Linux.

[kiview]

How is your build server setup? If the file is still there, can you please make a ls -la on the file and on your /target dir?

Sounds like something that might happen if the Docker container writes the files with root user id and so other users aren't allowed to move/delete it.

[kwbr]

The movie file is never created. The vcr-container dies instantly. The tests are run with an unprivileged user who has write permissons to the target/ directory

1a25bef353cf        richnorth/vnc-recorder:latest            "flvrec.py -o /recor…"   3 seconds ago       Exited (139) 1 second ago

It runs the Docker entrypoint with the following arguments

[-o /recording/screen.flv -P /recording/password vnchost 5900]

Quick googling for exit code 139: segfault?

Any idea how I can debug this further?

[kwbr]

BTW I can connect to the selenium/standalone-chrome-debug with VNC and see the test running.

[bsideup]

Hi @kwbr,
Good news - it's already fixed in #526 :) We will merge &release it soon, you can also try it yourself with jitpack:
https://www.testcontainers.org/usage.html#maven-dependencies

[kwbr]

Thanks, I'll test it out as soon as it's merged and released. Just subscribed for notifications on the issue.

[rnorth]

I suspect that, if not already fixed, #888 may finally fix this.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you believe this is a mistake, please reply to this comment to keep it open. If there isn't one already, a PR to fix or at least reproduce the problem in a test case will always help us get back on track to tackle this.

[stale]

This issue has been automatically closed due to inactivity. We apologise if this is still an active problem for you, and would ask you to re-open the issue if this is the case.