-
-
Notifications
You must be signed in to change notification settings - Fork 52
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
/opt/bin/Xvnc directory #174
Comments
|
thank you for the response. I tried downloading the container and reinstalling but I get the same results. when I look at the /opt directory I don't see /base/ [xxxxxxx@HomeNAS opt]$ ls -lart |
Did you removed the image (
You are looking at the host. You should instead look inside the container:
|
Thanks again for the quick response. It seems that the image may be corrupt based on the fact that no matter how many times I pull it, I continue to receive the permissions error. Below is the output of your last command. [xxxxxxx@HomeNAS ~]$ docker run --rm jlesage/makemkv ls -l /opt/base/bin |
If layers of the image are shared with other images, a |
I don't see a message 'Alerady exists' when completing the pull command: [xxxxxxx@HomeNAS ~]$ docker pull jlesage/makemkv |
Ok, then the problem might be something else. Do you see the same issue when you run:
|
This is the output of the command: [xxxxxxx@HomeNAS ~]$ docker run --rm jlesage/makemkv |
On what system are you running this container ? Looks like there is something specific on your system that prevent the container from running correctly. Is Docker itself up-to-date ? Do you have any filesystem ACLs in place? |
I'm running this on Qnap NAS Container station. it's up to date according to qnap. |
After installing and starting the container I get the following error. When I look at the /opt directory, there is no /base/bin/Xvnc. Is the container supposed to install xvnc during the installation process or is that something I need to install separately?
[supervisor ] starting services...
[supervisor ] starting service 'xvnc'...
[xvnc ] execve(/opt/base/bin/Xvnc): Permission denied
[supervisor ] service 'xvnc' failed to be started: not ready after 5000 msec, giving up.
[supervisor ] stopping service 'xvnc'...
[supervisor ] service 'xvnc' exited (with status 126).
[finish ] executing container finish scripts...
[finish ] all container finish scripts executed.
The text was updated successfully, but these errors were encountered: