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
This error is most likely due to the default UID/GID used in Kavita, which is discussed in here. However, that was last year.
Various resources online have suggested a workaround using the arg --no-same-owner, such as here.
To do so, we have to edit the _common.sh file to add an arg to the ynh_setup_source function's tar command. I have tried to edit the _common.sh and install scripts in a separate fork here, which allows the app to successfully install.
The text was updated successfully, but these errors were encountered:
Perhaps this --no-same-owner trick should go into core 🤔
The code should be reviewed before it goes into core. This was a quick 30 minute brainstorm, and I am no programmer - I've just seen enough code to be able to understand it, but not write it. I edit a lot, but don't really write anything since I don't got the knowledge for that.
If the edits are good, I am willing to request a pull. However, I am not sure if this fix will be permanent. If helpers were to ever change, it would break the app installation script most likely. That is pure speculation though.
Describe the bug
Install script fails after the unpacking phase. It is unable to set UID/GID with the error: Invalid argument.
This might be only relevant to LXCs.
Context
Steps to reproduce
Expected behavior
Successful install.
Logs
The log can be found here.
This error is most likely due to the default UID/GID used in Kavita, which is discussed in here. However, that was last year.
Various resources online have suggested a workaround using the arg
--no-same-owner
, such as here.To do so, we have to edit the
_common.sh
file to add an arg to theynh_setup_source
function'star
command. I have tried to edit the_common.sh
andinstall
scripts in a separate fork here, which allows the app to successfully install.The text was updated successfully, but these errors were encountered: