andrey-yantsen
test: Embed the test data inside the test container image
This is something of a test to see if it might resolve #541. I discovered that running tests locally got a lot better when switching Docker Desktop's file sharing implementation from VirtioFS to gRPC FUSE which got me wondering whether bind mounting the data into the container is an issue. That would seem strange since that's how I run my own server but still I thought it might be worth a try. This change creates a new container image where instead of mounting the data we copy it into the image before launching so there are no longer any bind mounts involved.
Unfortunately, I don't think it'll help us to resolve the transcoding crashes in any way :( Volumes on macOS and Linux work in very different ways.
Just to clarify my previous comment(s), as I think I didn't communicate my thoughts clearly. I'll do my best to avoid providing quick-ish responses during business hours in the future.
The change is good and valuable: it solves the issue arising during the development using macOS. But it doesn't look like it might fix the problem with crashes during transcoding requests :(
Just to clarify my previous comment(s), as I think I didn't communicate my thoughts clearly. I'll do my best to avoid providing quick-ish responses during business hours in the future.
The change is good and valuable: it solves the issue arising during the development using macOS. But it doesn't look like it might fix the problem with crashes during transcoding requests :(
You're probably right. So I guess the question is do you think it is actually worth doing this? It will slow down running tests, though should be by a pretty tiny amount and I guess adds an additional point of failure.
Let's keep this open for now and use the old flow locally. If the issue with the missed media will show itself in the next, let's say, month, it'll be a good sign that we need this change.