NodeBB 1.18.0 docker update

MaxWaldorf

Hi team,

Is it expected to have no docker image yet for 1.18.0?

I am running nodebb on kubernetes so I can't upgrade without a new image.

BTW, do you need help to make cross platform images (support for arm would be appreciated)

Cheers

julian

@maxwaldorf Hi Max, it seems our integration that automatically created docker images is now a paid-only option, so that explains why it stopped.

I have manually pushed an image up for v1.18.2, although I cannot vouch for its reliability since it is my first time doing so

An alternative Docker image would be https://hub.docker.com/r/nilsramsperger/nodebb/

This one is kept fairly up to date by a third-party.

MaxWaldorf

@julian the image doesn't work...

It seems that there is a right issue on plugins folder...

I am getting the error:

started
2021-09-08T22:51:51.888Z [4567/8] - error: [build] Encountered error preparing for build
Error: [[error:theme-not-found]]
    at Themes.setupPaths (/usr/src/app/src/meta/themes.js:151:9)
    at async beforeBuild (/usr/src/app/src/meta/build.js:68:3)
    at async exports.build (/usr/src/app/src/meta/build.js:165:3)
    at async Object.buildWrapper [as build] (/usr/src/app/src/cli/manage.js:147:3)
2021-09-08T22:51:51.889Z [4567/8] - error: [build] Encountered error during build step
Error: [[error:theme-not-found]]
    at Themes.setupPaths (/usr/src/app/src/meta/themes.js:151:9)
    at async beforeBuild (/usr/src/app/src/meta/build.js:68:3)
    at async exports.build (/usr/src/app/src/meta/build.js:165:3)
    at async Object.buildWrapper [as build] (/usr/src/app/src/cli/manage.js:147:3)
2021-09-08T22:51:51.889Z [4567/8] - error: Error: [[error:theme-not-found]]
    at Themes.setupPaths (/usr/src/app/src/meta/themes.js:151:9)
    at async beforeBuild (/usr/src/app/src/meta/build.js:68:3)
    at async exports.build (/usr/src/app/src/meta/build.js:165:3)
    at async Object.buildWrapper [as build] (/usr/src/app/src/cli/manage.js:147:3)
Starting NodeBB
  "./nodebb stop" to stop the NodeBB server
  "./nodebb log" to view server output
  "./nodebb help" for more commands
NodeBB v1.18.0 Copyright (C) 2013-2014 NodeBB Inc.
This program comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it under certain conditions.
For the full license, please visit: http://www.gnu.org/copyleft/gpl.html
Clustering enabled: Spinning up 1 process(es).
2021-09-08T22:51:53.005Z [4567/37] - info: Initializing NodeBB v1.18.0 https://redacted-on-purpose
2021-09-08T22:51:54.484Z [4567/37] - warn: [meta/dependencies] Bundled plugin nodebb-theme-persona not found, skipping dependency check.
2021-09-08T22:51:54.485Z [4567/37] - warn: [meta/dependencies] Bundled plugin nodebb-theme-vanilla not found, skipping dependency check.
2021-09-08T22:51:54.877Z [4567/37] - info: [socket.io] Restricting access to origin: https://redacted-on-purpose:*
2021-09-08T22:51:54.938Z [4567/37] - error: Error: [[error:theme-not-found]]
    at Themes.setupPaths (/usr/src/app/src/meta/themes.js:151:9)
    at async initializeNodeBB (/usr/src/app/src/webserver.js:98:2)
    at async exports.listen (/usr/src/app/src/webserver.js:83:2)
    at async Object.start.start (/usr/src/app/src/start.js:45:3)
[cluster] Child Process (37) has exited (code: 0, signal: null)

A couple more investigation shows:

npm WARN checkPermissions Missing write access to /usr/src/app/node_modules/nodebb-plugin-aliases
npm WARN checkPermissions Missing write access to /usr/src/app/node_modules/nodebb-plugin-composer-quill
npm WARN checkPermissions Missing write access to /usr/src/app/node_modules/nodebb-plugin-email-helper
npm WARN checkPermissions Missing write access to /usr/src/app/node_modules/nodebb-plugin-emailer-sendgrid
npm WARN checkPermissions Missing write access to /usr/src/app/node_modules/nodebb-plugin-geofence
npm WARN checkPermissions Missing write access to /usr/src/app/node_modules/nodebb-plugin-leaderboard
npm WARN checkPermissions Missing write access to /usr/src/app/node_modules/nodebb-plugin-registration-notification
npm WARN checkPermissions Missing write access to /usr/src/app/node_modules/nodebb-plugin-warnings
npm WARN checkPermissions Missing write access to /usr/src/app/node_modules/nodebb-theme-persona
npm WARN checkPermissions Missing write access to /usr/src/app/node_modules/nodebb-theme-vanilla
npm WARN checkPermissions Missing write access to /usr/src/app/node_modules/quill
npm ERR! code ENOENT
npm ERR! syscall access
npm ERR! path /usr/src/app/node_modules/nodebb-plugin-aliases
npm ERR! errno -2
npm ERR! enoent ENOENT: no such file or directory, access '/usr/src/app/node_modules/nodebb-plugin-aliases'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent

So I guess this is a folder rights issues...

julian

@maxwaldorf any luck with the nilsramsperger build?

We're working on getting the docker pushes up and running again but it will be awhile

MaxWaldorf

@julian he is using an embedded redis cache...
I am using mongo right now... Plus, I would need to remap all my volumes without really knowing what would be the consequences...

So that would be a no go...

But don't worry I can wait a couple days for you guys to sort this out.

Let me know if I can help as well...

Cheers

fais3000

@maxwaldorf You can try https://hub.docker.com/r/nibrev/nodebb/tags. I just used the latest image to update to 1.18.0

Here is my nodebb docker setup.

enot

@fais3000 said in NodeBB 1.18.0 docker update:

@maxwaldorf You can try https://hub.docker.com/r/nibrev/nodebb/tags. I just used the latest image to update to 1.18.0

Here is my nodebb docker setup.

This is the image I use, although I'm not using Mongo so unsure if it works for you.

julian

@fais3000 glad to hear we have so many community images on docker @Antosik is helping us resolve our issues with the docker builds

MaxWaldorf

@enot I usually stick to the official image as I work on Kubernetes and changing my setup isn't really something I like doing (I have an entire backup infrastructure setup around it)

Plus, if the maintainer doesn't support it anymore, it means I have to revert to another solution.

As said, I am cool with waiting the official image to be updated

julian

@maxwaldorf we've a new image pushed now, I think... Can you try with latest?

MaxWaldorf

@julian Bingo!

This image works!
I guess you can delete the v1.18.2 image and regenerate it with this build.

Good work!

Cheers

julian

@maxwaldorf I just deleted the 1.18.2 tag from Docker Hub -- I most likely won't regenerate the image. v1.18.3 will be the next release with a Docker image.