Open DJJazzyMike opened 1 year ago
/opt/base/bin/Xvnc
should definitely be there. Permission denied
usually indicates that the file is there, but it doesn't have the correct permissions. Looks like the installed image is corrupted on your system.
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 total 8 -rw-r--r-- 1 admin administrators 4571 2023-04-20 19:08 nasconfig_fs.img.tgz lrwxrwxrwx 1 admin administrators 54 2023-05-21 03:15 kata -> /share/CACHEDEV1_DATA/.qpkg/container-station/opt/kata/ drwx--s--x 4 admin administrators 80 2023-05-21 03:15 containerd/ drwxr-sr-x 3 mwierm administrators 100 2023-05-21 03:15 ./ drwxr-xr-x 24 admin administrators 620 2023-05-21 03:17 ../
I tried downloading the container and reinstalling but I get the same results
Did you removed the image (docker rmi jlesage/makemkv
) ? Also, when you download the image again (docker pull jlesage/makemkv
), make sure you don't see output like this:
...
63b65145d645: Already exists
4f4fb700ef54: Already exists
f9305ddce4c8: Already exists
59c53306de0a: Already exists
a8eb0c2634d0: Already exists
6a99d85f6c90: Already exists
3215f7b0a884: Already exists
...
when I look at the /opt directory I don't see /base/
[xxxxxxx@HomeNAS opt]$ ls -lart
You are looking at the host. You should instead look inside the container:
docker run --rm jlesage/makemkv ls -l /opt/base/bin
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 total 14136 -rwxr-xr-x 1 root root 2836432 Apr 16 17:14 Xvnc -rwxr-xr-x 1 root root 2320 Mar 3 22:41 add-pkg -rwxr-xr-x 1 root root 1178 Mar 3 22:41 del-pkg -rwxr-xr-x 1 root root 5651 Mar 3 22:41 install-glibc -rwxr-xr-x 1 root root 7739 Apr 16 15:57 install_app_icon.sh -rwxr-xr-x 1 root root 637 Mar 3 22:41 is-bool-val-false -rwxr-xr-x 1 root root 634 Mar 3 22:41 is-bool-val-true -rwxr-xr-x 1 root root 35416 Mar 3 22:42 logmonitor -rwxr-xr-x 1 root root 1015508 Apr 16 16:33 obxprop -rwxr-xr-x 1 root root 3143996 Apr 16 16:33 openbox -rwxr-xr-x 1 root root 893 Mar 3 22:41 sed-patch -rwxr-xr-x 1 root root 969 Mar 3 22:41 set-cont-env -rwxr-xr-x 1 root root 3140 Mar 3 22:41 take-ownership -rwxr-xr-x 1 root root 72408 Apr 16 16:51 vncpasswd -rwxr-xr-x 1 root root 603604 Apr 16 15:59 xdpyprobe -rwxr-xr-x 1 root root 1284360 Apr 16 17:16 xkbcomp -rwxr-xr-x 1 root root 5424244 Apr 16 17:19 yad
If layers of the image are shared with other images, a docker rmi
won't remove them. Thus the reason for checking the output of the docker pull
command for Already exists
lines. Did you see them ?
I don't see a message 'Alerady exists' when completing the pull command:
[xxxxxxx@HomeNAS ~]$ docker pull jlesage/makemkv
Using default tag: latest
latest: Pulling from jlesage/makemkv
ef5531b6e74e: Pulling fs layer
4f4fb700ef54: Pull complete
84e5e0a543c2: Pull complete
ca8059c6dc96: Pull complete
f71b9399bd0c: Pull complete
e933e7e0c508: Pull complete
017a64d4a562: Pull complete
7507c5a91d58: Pull complete
275cabea4fa3: Pull complete
cc9a6af94887: Pull complete
9c93353b9182: Pull complete
46dd2ad46dad: Pull complete
e5c7dd7860e7: Pull complete
f618247ab108: Pull complete
123f74ff7a01: Pull complete
6334a09260dd: Pull complete
16054b67208f: Pull complete
ff2d8d94a0d9: Pull complete
bcb1c2b4296e: Pull complete
e058071a46f7: Pull complete
c4a088cf96a0: Pull complete
a1874aba1e4f: Pull complete
94691590ba1c: Pull complete
cb92b70ab2c5: Pull complete
e683f627b9c4: Pull complete
e35226ef7dc2: Pull complete
227f6730f266: Pull complete
6cae747d788e: Pull complete
4775b1fb1e1a: Pull complete
88d45bffc6b2: Pull complete
1483b1790e30: Pull complete
c377ccf27011: Pull complete
7215505a1e74: Pull complete
Digest: sha256:bf014c2e1a96917776a701e3fec3a663642f08848f7277e3beb73f675847f35f
Status: Downloaded newer image for jlesage/makemkv:latest
docker.io/jlesage/makemkv:latest
Ok, then the problem might be something else. Do you see the same issue when you run:
docker run --rm jlesage/makemkv
This is the output of the command:
[xxxxxxx@HomeNAS ~]$ docker run --rm jlesage/makemkv [init ] container is starting... [cont-env ] loading container environment variables... [cont-env ] APP_NAME: loading... [cont-env ] APP_VERSION: loading... [cont-env ] DISPLAY: executing... [cont-env ] DISPLAY: terminated successfully. [cont-env ] DISPLAY: loading... [cont-env ] DOCKER_IMAGE_PLATFORM: loading... [cont-env ] DOCKER_IMAGE_VERSION: loading... [cont-env ] GTK2_RC_FILES: executing... [cont-env ] GTK2_RC_FILES: terminated successfully. [cont-env ] GTK2_RC_FILES: loading... [cont-env ] GTK_THEME: executing... [cont-env ] GTK_THEME: terminated successfully. [cont-env ] GTK_THEME: loading... [cont-env ] HOME: loading... [cont-env ] QT_STYLE_OVERRIDE: executing... [cont-env ] QT_STYLE_OVERRIDE: terminated successfully. [cont-env ] QT_STYLE_OVERRIDE: loading... [cont-env ] SUP_GROUP_IDS_INTERNAL: executing... [cont-env ] SUP_GROUP_IDS_INTERNAL: terminated successfully. [cont-env ] SUP_GROUP_IDS_INTERNAL: loading... [cont-env ] TAKE_CONFIG_OWNERSHIP: loading... [cont-env ] XDG_CACHE_HOME: loading... [cont-env ] XDG_CONFIG_HOME: loading... [cont-env ] XDG_DATA_HOME: loading... [cont-env ] XDG_RUNTIME_DIR: loading... [cont-env ] XDG_STATE_HOME: loading... [cont-env ] container environment variables initialized. [cont-secrets] loading container secrets... [cont-secrets] container secrets loaded. [cont-init ] executing container initialization scripts... [cont-init ] 10-certs.sh: executing... [cont-init ] 10-certs.sh: terminated successfully. [cont-init ] 10-check-app-niceness.sh: executing... [cont-init ] 10-check-app-niceness.sh: terminated successfully. [cont-init ] 10-cjk-font.sh: executing... [cont-init ] 10-cjk-font.sh: terminated successfully. [cont-init ] 10-clean-logmonitor-states.sh: executing... [cont-init ] 10-clean-logmonitor-states.sh: terminated successfully. [cont-init ] 10-clean-tmp-dir.sh: executing... [cont-init ] 10-clean-tmp-dir.sh: terminated successfully. [cont-init ] 10-fontconfig-cache-dir.sh: executing... [cont-init ] 10-fontconfig-cache-dir.sh: terminated successfully. [cont-init ] 10-init-users.sh: executing... [cont-init ] 10-init-users.sh: terminated successfully. [cont-init ] 10-nginx.sh: executing... [cont-init ] 10-nginx.sh: terminated successfully. [cont-init ] 10-openbox.sh: executing... [cont-init ] 10-openbox.sh: terminated successfully. [cont-init ] 10-set-tmp-dir-perms.sh: executing... [cont-init ] 10-set-tmp-dir-perms.sh: terminated successfully. [cont-init ] 10-vnc-password.sh: executing... [cont-init ] 10-vnc-password.sh: terminated successfully. [cont-init ] 10-web-data.sh: executing... [cont-init ] 10-web-data.sh: terminated successfully. [cont-init ] 10-x11-unix.sh: executing... [cont-init ] 10-x11-unix.sh: terminated successfully. [cont-init ] 10-xdg-runtime-dir.sh: executing... [cont-init ] 10-xdg-runtime-dir.sh: terminated successfully. [cont-init ] 15-install-pkgs.sh: executing... [cont-init ] 15-install-pkgs.sh: terminated successfully. [cont-init ] 54-check-optical-drive.sh: executing... [cont-init ] 54-check-optical-drive.sh: looking for usable optical drives... [cont-init ] 54-check-optical-drive.sh: found optical drive [-, /dev/sg4], but it is not usable because: [cont-init ] 54-check-optical-drive.sh: --> the host device - is not exposed to the container. [cont-init ] 54-check-optical-drive.sh: --> the host device /dev/sg4 is not exposed to the container. [cont-init ] 54-check-optical-drive.sh: no usable optical drive found. [cont-init ] 54-check-optical-drive.sh: terminated successfully. [cont-init ] 55-makemkv.sh: executing... [cont-init ] 55-makemkv.sh: generating machine-id... [cont-init ] 55-makemkv.sh: '/defaults/settings.conf' -> '/config/settings.con f' [cont-init ] 55-makemkv.sh: '/defaults/QtProject.conf' -> '/config/xdg/config/ QtProject.conf' [cont-init ] 55-makemkv.sh: checking for new beta key... [cont-init ] 55-makemkv.sh: registration key already up-to-date. [cont-init ] 55-makemkv.sh: getting supported drives... [cont-init ] 55-makemkv.sh: terminated successfully. [cont-init ] 85-take-config-ownership.sh: executing... [cont-init ] 85-take-config-ownership.sh: terminated successfully. [cont-init ] 89-info.sh: executing... ╭――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――╮ │ │ │ Application: MakeMKV │ │ Application Version: 1.17.3 │ │ Docker Image Version: 23.04.2 │ │ Docker Image Platform: linux/amd64 │ │ │ ╰――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――╯ [cont-init ] 89-info.sh: terminated successfully. [cont-init ] all container initialization scripts executed. [init ] giving control to process supervisor. [supervisor ] loading services... [supervisor ] loading service 'default'... [supervisor ] loading service 'app'... [supervisor ] loading service 'gui'... [supervisor ] loading service 'certsmonitor'... [supervisor ] service 'certsmonitor' is disabled. [supervisor ] loading service 'nginx'... [supervisor ] loading service 'xvnc'... [supervisor ] loading service 'openbox'... [supervisor ] loading service 'logmonitor'... [supervisor ] service 'logmonitor' is disabled. [supervisor ] loading service 'logrotate'... [supervisor ] loading service 'autodiscripper-0'... [supervisor ] service 'autodiscripper-0' is disabled. [supervisor ] loading service 'autodiscripper-1'... [supervisor ] service 'autodiscripper-1' is disabled. [supervisor ] loading service 'autodiscripper-10'... [supervisor ] service 'autodiscripper-10' is disabled. [supervisor ] loading service 'autodiscripper-11'... [supervisor ] service 'autodiscripper-11' is disabled. [supervisor ] loading service 'autodiscripper-12'... [supervisor ] service 'autodiscripper-12' is disabled. [supervisor ] loading service 'autodiscripper-13'... [supervisor ] service 'autodiscripper-13' is disabled. [supervisor ] loading service 'autodiscripper-14'... [supervisor ] service 'autodiscripper-14' is disabled. [supervisor ] loading service 'autodiscripper-15'... [supervisor ] service 'autodiscripper-15' is disabled. [supervisor ] loading service 'autodiscripper-2'... [supervisor ] service 'autodiscripper-2' is disabled. [supervisor ] loading service 'autodiscripper-3'... [supervisor ] service 'autodiscripper-3' is disabled. [supervisor ] loading service 'autodiscripper-4'... [supervisor ] service 'autodiscripper-4' is disabled. [supervisor ] loading service 'autodiscripper-5'... [supervisor ] service 'autodiscripper-5' is disabled. [supervisor ] loading service 'autodiscripper-6'... [supervisor ] service 'autodiscripper-6' is disabled. [supervisor ] loading service 'autodiscripper-7'... [supervisor ] service 'autodiscripper-7' is disabled. [supervisor ] loading service 'autodiscripper-8'... [supervisor ] service 'autodiscripper-8' is disabled. [supervisor ] loading service 'autodiscripper-9'... [supervisor ] service 'autodiscripper-9' is disabled. [supervisor ] loading service 'autodiscripper'... [supervisor ] service 'autodiscripper' is disabled. [supervisor ] all services loaded. [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, g iving up. [supervisor ] stopping service 'xvnc'... [supervisor ] service 'xvnc' exited (with status 126). [finish ] executing container finish scripts... [finish ] all container finish scripts executed.
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.