-
Notifications
You must be signed in to change notification settings - Fork 5.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Oops caused by install plugins in discourse #75943
Comments
I got the cause, which is I didn't migrate the database. But when I do it, there are still some errors:
Likely Rails gem is out of date. Maybe base image might be a little old. I don't know whether it will be OK if upgrade ruby to 3.3.6. |
This error may be caused by discourse-assign plugin. Discourse-solved plugin doesn't work well too. |
Hi @IshuaWang, I tried to reproduce the issue, but the plugin installation worked fine. I used the Bitnami Discourse chart for this, didn't use the container, due to it implements the logic to install plugins https://github.com/bitnami/charts/blob/main/bitnami/discourse/templates/deployment.yaml#L107 If you take a look at it, it not only runs the install command but also the update_all and pull_compatible_all ones. Remember to use "discourse" as user when running the commands so you do not run into permissions issues. After that, the plugin works as expected |
thanks for your efforts. I will try later with discourse user. |
Name and Version
bitnami/discourse:3.3.3
What architecture are you using?
amd64
What steps will reproduce the bug?
Install the app using the docker file on ubuntu22.
Then, log in to the container and install some plugins provided by official websites according to your instructions.
the plugs are as follows, actually, I just tried some of them and they will trigger the error.
Then if you refresh the page /admin/plugins, the error of Oop occurs, which causes you to have to reinstall discourse.
What is the expected behavior?
It should run without errors.
What do you see instead?
I reinstalled the app, so the previous log is missing. But I will offer the log using the current container later. Here are some logs:
The text was updated successfully, but these errors were encountered: