Docker WBO KO sur Synology about whitebophir

[lovasoa]

@mariushosting : thanks ! this is a useful report. I'll look into it.

[mariushosting]

@lovasoa @KaaR0l downgrade to version 1.19.1 since the latest update 1.20.0 broke something

docker run -d --name=wbo
-p 5479:80
-v /volume1/docker/wbo:/opt/app/server-data
--restart always
lovasoa/wbo:v1.19.1
chown -R 1000:1000 /volume1/docker/wbo

For @lovasoa this is the error log with the latest 1.20.0 version:

at emitErrorNT (net.js:1358:8)
at processTicksAndRejections (internal/process/task_queues.js:82:21) {

code: 'EACCES',
errno: -13,
syscall: 'listen',
address: '0.0.0.0',
port: 80
}
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start: node ./server/server.js
npm ERR! Exit status 1
�

npm ERR! Failed at the [email protected] start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/node/.npm/_logs/2023-11-30T10_12_11_354Z-debug.log

[email protected] start /opt/app
node ./server/server.js
server started {"port":80}
events.js:377
throw er; // Unhandled 'error' event
^
Error: listen EACCES: permission denied 0.0.0.0:80
at Server.setupListenHandle [as _listen2] (net.js:1314:21)
at listenInCluster (net.js:1379:12)
at Server.listen (net.js:1465:7)
at Object. (/opt/app/server/server.js:30:5)
at Module._compile (internal/modules/cjs/loader.js:1114:14)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1143:10)
at Module.load (internal/modules/cjs/loader.js:979:32)
at Function.Module._load (internal/modules/cjs/loader.js:819:12)
at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:75:12)
at internal/main/run_main_module.js:17:47
Emitted 'error' event on Server instance at:
at emitErrorNT (net.js:1358:8)
at processTicksAndRejections (internal/process/task_queues.js:82:21) {
code: 'EACCES',
errno: -13,
syscall: 'listen',
address: '0.0.0.0',
port: 80
}
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start: node ./server/server.js
npm ERR! Exit status

[lovasoa]

Bonjour,
Il n'y a pas d'erreur dans les logs que vous mentionnez :) Je ne connais pas synology, mais peut-être devriez-vous demander de l'aide à la personne qui a écrit ce tutoriel ?

[lovasoa]

Vous pouvez toujours commenter ci-dessous, mais je préfère fermer l'issue si ce n'est pas un problème avec wbo.

[KaaR0l]

Bonjour,
Et merci pour votre réponse.
Je vais chercher de l'autre côté.
Bonne journée,
Carole.

[lovasoa]

Bonne journée à vous ! N'hésitez pas à poster ici si vous trouvez une solution, ou si vous trouvez des logs d'erreurs de wbo.

[lovasoa]

Looks like our arm image builds don't work anymore, which prevents anything from being pushed to docker.

I manually updated images for intel and arm64: https://hub.docker.com/repository/docker/lovasoa/wbo/general

As for the port binding error, I'm not sure it's related, but you can always specify the port on which you want to have wbo listen. Your launch command could look like this:

docker run -d --name=wbo -p 5479:5479 -e PORT=5479 -v /volume1/docker/wbo:/opt/app/server-data --restart always lovasoa/wbo:latest

[mariushosting]

Looks like our arm image builds don't work anymore, which prevents anything from being pushed to docker.

I manually updated images for intel and arm64: https://hub.docker.com/repository/docker/lovasoa/wbo/general

As for the port binding error, I'm not sure it's related, but you can always specify the port on which you want to have wbo listen. Your launch command could look like this:

docker run -d --name=wbo -p 5479:5479 -e PORT=5479 -v /volume1/docker/wbo:/opt/app/server-data --restart always lovasoa/wbo:latest

This completely solved the issue!

Thank you for the effort @lovasoa