Adjust init-permission/run to finish correctly on qnap#252
Adjust init-permission/run to finish correctly on qnap#252klepek wants to merge 3 commits intolinuxserver:masterfrom
Conversation
describe changes for 04.01.25
There was a problem hiding this comment.
Thanks for opening this pull request! Be sure to follow the pull request template!
|
I am a bot, here is the pushed image/manifest for this PR:
|
|
I have this issue as well. Do we know if there is a workaround whilst the issue is being resolved? |
|
We're not going to override base init in downstream images as that way madness lies. The issue has been reported to QNAP and they've accepted it as a bug but there's no indication is to if/when they will fix it. We've paused any further rebases for nginx-based images for the moment which should prevent any more being affected. In the meantime any affected images will need to be pinned to versions from before they were rebased to 3.21. We're not going to start applying workarounds because they all involve potentially masking actual errors that could impact other non-QNAP users. |
Description:
init-permission now finishes even when chmod have issue
Benefits of this PR and context:
closes #251
How Has This Been Tested?
package build, package execution and confirmation that it starts
Source / References:
simmilar fix: linuxserver/docker-swag#514