You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thank you for implementing #133, however when setting those env the container does not start with the following message:
sh: java: not found
usermod: no changes
sh: java: not found
usermod: no changes
sh: java: not found
usermod: no changes
sh: java: not found
usermod: no changes
sh: java: not found
usermod: no changes
sh: java: not found
usermod: no changes
sh: java: not found
When the envs are removed the container works fine.
It looks like the PATH env variable is not working, maybe try addin -m or -p to the su command. Since i have limited docker support on the QNAP i cannot test it with a newly build container.
The text was updated successfully, but these errors were encountered:
Container does not start on QNAP NAS when using env GID and PUID.
Command line I used to start the container
Press start in the QNAP Container Station GUI
Steps to reproduce the issue:
Create a new container
Set env GID and PUID
Start the container
Describe the results you received:
Container does not start
Describe the results you expected:
Container should start and create downloaded files with the given chown & chgrp of the values in PUID and GID
Additional information you deem important (e.g. issue happens only occasionally):
QNAP TS-462
QTS 5.2.2.2950
Container Station
Version 3.0.9.1038 (2024/11/08)
Without PUID and GID the container is starting. (eg. not launched via su as stated in the entrypoint script)
Provide some logs (docker logs jdownloader)
sh: java: not found
usermod: no changes
sh: java: not found
usermod: no changes
sh: java: not found
usermod: no changes
sh: java: not found
usermod: no changes
sh: java: not found
usermod: no changes
sh: java: not found
usermod: no changes
sh: java: not found
Thank you for implementing #133, however when setting those env the container does not start with the following message:
When the envs are removed the container works fine.
It looks like the PATH env variable is not working, maybe try addin -m or -p to the su command. Since i have limited docker support on the QNAP i cannot test it with a newly build container.
The text was updated successfully, but these errors were encountered: