YunoHost-Apps / discourse_ynh

Discourse package for YunoHost
https://www.discourse.org/
GNU General Public License v2.0
24 stars 12 forks source link

Install fails on "npm ERR! An unknown git error occurred" #166

Closed b01xy closed 5 months ago

b01xy commented 1 year ago

Describe the bug

The install process of Discourse fails on Yunohost 11.2.5 Debian 11 inside an LXC container beside an apache2 reverse proxy

Context

While trying to install Discourse via CLI on a dedicated sub-domain (forum.mydomain.org/), the install fails with this errors / warnings :

2023-11-20 22:28:46,733: WARNING - npm notice
2023-11-20 22:28:46,734: WARNING - npm notice New major version of npm available! 8.5.0 -> 10.2.4
2023-11-20 22:28:46,734: WARNING - npm notice Changelog: <https://github.com/npm/cli/releases/tag/v10.2.4>
2023-11-20 22:28:46,734: WARNING - npm notice Run `npm install -g npm@10.2.4` to update!
2023-11-20 22:28:46,734: WARNING - npm notice
2023-11-20 22:28:46,734: WARNING - npm ERR! code 128
2023-11-20 22:28:46,734: WARNING - npm ERR! An unknown git error occurred
2023-11-20 22:28:46,735: WARNING - npm ERR! command git --no-replace-objects ls-remote ssh://git@github.com/lodash-archive/lodash-cli.git
2023-11-20 22:28:46,735: WARNING - npm ERR! git@github.com: Permission denied (publickey).
2023-11-20 22:28:46,735: WARNING - npm ERR! fatal: Could not read from remote repository.
2023-11-20 22:28:46,735: WARNING - npm ERR!
2023-11-20 22:28:46,735: WARNING - npm ERR! Please make sure you have the correct access rights
2023-11-20 22:28:46,735: WARNING - npm ERR! and the repository exists.
2023-11-20 22:28:46,736: DEBUG - 
2023-11-20 22:28:46,736: WARNING - npm ERR! A complete log of this run can be found in:
2023-11-20 22:28:46,736: WARNING - npm ERR!     /root/.npm/_logs/2023-11-20T21_27_48_653Z-debug-0.log
2023-11-20 22:28:46,747: DEBUG - + ynh_exit_properly
2023-11-20 22:28:46,747: DEBUG - + local exit_code=128

Full log here https://paste.yunohost.org/raw/acuxigexab

Did I missed something or is it due to my LXC context ?

Salamandar commented 5 months ago

Should be fixed by packagingv2.