-
-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failing to start with NFS-mounted output #115
Comments
Did you check that the user configured as |
Yes, it does seem to have write access. I spun up a second container of
(I know the
And I can verify that the So (to me) it looks like a weird interaction between Also, my issue and pull request on your HandBrake repo are the same issue and resolution. |
To have a complete picture of the problem, could you provide the output of I think that it should be possible to fix the check itself. |
|
I adjusted the write test. Can you try the latest image to see if it fixes your issue ? |
Yes, that works great! Thank you for changing it. I do still have to run it with the Also, I know it's a lot to ask, but would you be able to adapt https://github.com/jlesage/docker-handbrake and https://github.com/jlesage/docker-mkvtoolnix to use this check too? I want to use them too, but this issue stops me with them as well. Much thanks! |
Thanks for confirming that the And yes, I will make sure other contains are also fixed. There are no new images yet, but the fix for the |
Shouldn't you simply use the mount type nfs for the volume itself instead of tweaking that in the container? |
@34will, do you still have the same setup? I would be interested in your NFS server configuration. |
When the
/output
volume is mounted to an NFS (v4) share, the container fails to start with the error:However I can confirm that I can write to the location.
The text was updated successfully, but these errors were encountered: