https://github.com/NodeBB/NodeBB/issues/9772 There was a bug that was causing the messaging to now show up when someone was added to the queue. Thanks for reporting.
Docker issues
-
Hello,
i am having a bad time trying to get nodebb running in docker. I found several images and such, most are out of date and dont support postgres. The official docker image doesnt have Persistant storage support
The only thing i got running was https://github.com/rez0n/docker-nodebb but even that makes issues with plugins, a user openend an issue about it but it never got respond to
(https://github.com/rez0n/docker-nodebb/issues/156)
Does anyone know how to fix the issue above? And if not, is there a chance that we can get better docker support for nodebb by the official image?
-
@iltyak Here is my Docker Nodebb setup setup for DiscussPlaces. It uses the nodebb image from rez0n and mongodb image for bitnami. You can try it out and let me know if you are stuck and I will try to help.
-
@fais3000 Hello,
i use the same image and have issues with plugins like mentioned above (https://github.com/rez0n/docker-nodebb/issues/156) your setup doesnt have much difference, only that you use mongodb and i use postgres.
Could you check if you have the same issue if you docker-compose down and up?
-
@iltyak No, for some reason I don't face such issue when i build.
-
@fais3000 Hello, with your setup it doesnt work at all. Are you sure thats your current setup?
-
@iltyak Yes, that's exactly what I'm running.
What errors do you see?
Also, i can see in bitnami docs that they are defaulting to non-root containers for better security so maybe that's what blocking you. What that means is that your db volume folder needs to give access to 1001 user.
You can remove following from the docker-compose file and give permissions to your shared volume and then try again.
user:root
chown -R 1001:1001 mongodb_data/
I've also updated my blog post
PS. Instead of nibrev/nodebb:beta you can use the latest stable release, which is nibrev/nodebb:latest
-
@fais3000 said in Docker issues:
which
Hello, here is the first error when docker-compose up after filling out the .env
ERROR: Named volume "local:/bitnami/mongodb:rw" is used in service "mongodb" but no declaration was found in the volumes section.
then after trying to fix this issue, the mongodb container is just loop restarting.
Then the nodebb container complains:
warn: NodeBB Setup Aborted. MongoServerSelectionError: getaddrinfo ENOTFOUND mongodb
I would like to use your setup but i really want to use postgres.
-
@iltyak said in Docker issues:
claration was found in the volumes section.
Please re-verify the volume directives.
I am running another nodebb instance inside a folder /var/www/containerized/ through following file you can try this. Make sure to remove orphan containers and volumes to avoid confusion.
version: "3.3" services: nodebb: container_name: ${PROJECT_NAME} ports: - "4567:4567" restart: unless-stopped volumes: - /var/www/containerized/${PROJECT_NAME}:/data environment: - URL=${URL} #Nodebb URL for config.js - DB_HOST=mongodb:27017 - DATABASE=mongo - DB_PORT="27017" - DB_USER=${DB_USER} - DB_PASSWORD=${DB_PASSWORD} image: "nibrev/nodebb:latest" depends_on: - mongodb links: - mongodb networks: - mongodb_network mongodb: container_name: ${PROJECT_NAME}_mongodb image: "docker.io/bitnami/mongodb:4.4" environment: - MONGODB_USERNAME=${MONGODB_USERNAME} - MONGODB_PASSWORD=${MONGODB_PASSWORD} - MONGODB_DATABASE=${MONGODB_DATABASE} - MONGODB_ROOT_PASSWORD=${MONGODB_ROOT_PASSWORD} restart: unless-stopped volumes: - "/var/www/containerized/${PROJECT_NAME}/${PROJECT_NAME}_mongodb_data:/bitnami/mongodb" networks: - mongodb_network volumes: mongodb_data: driver: local networks: mongodb_network: driver: bridge
If you wanna use postgres you can use bitnami's postgres image. It should be similar to mongodb https://github.com/bitnami/bitnami-docker-postgresql/blob/master/docker-compose.yml (i have not used it myself though)
-
@fais3000 Okay thank you i can try, one question; what is supposed to stay in there?
NODEBB_VOLUME_PATH=
and
MONGODB_VOLUME_PATH=I dont see any reference in the docker compose
-
@iltyak Volume paths are pointing to the docker-compose file in the blog post for nodebb and mongodb respectively.
The docker-compose file I gave you doesn't use those variable as we create the paths using the project name. You can choose either of the approaches.
Suggested Topics
-
Unsolved Issues with registration process
Technical Support • • zandertrek