greenlight
greenlight copied to clipboard
bigbluebutton
bundler: command not found: rake
Hi,
I'm using the latest docker image (2031c9e86d82), but it crashes quite immediately with the following messages:
`/root` is not writable. Bundler will use `/tmp/bundler20220509-10-3136e210' as your home directory temporarily. bundler: command not found: rake Install missing gem executables with `bundle install`
>>> Database initialization
`/root` is not writable.
Bundler will use `/tmp/bundler20220509-11-lg3z3x11' as your home directory temporarily.
bundler: command not found: rake
Install missing gem executables with `bundle install`
`/root` is not writable.
Bundler will use `/tmp/bundler20220509-12-yggyp312' as your home directory temporarily.
bundler: command not found: rake
Install missing gem executables with `bundle install`
`/root` is not writable.
Bundler will use `/tmp/bundler20220509-1-1dm9v151' as your home directory temporarily.
bundler: command not found: puma
Install missing gem executables with `bundle install`
Same problem here. We had to roll back to 2.11.2 as well. Are there any suggestions to solve this problem for 2.12.5?
Sorry for the direct ping @jfederico but could someone take a look at this? If access is needed to such a faulty setup I can provide it.
It is strange, I have that very same version working in production as https://demo.bigbluebutton.org. But it is deployed in a different way. I am using k8s for that one. The image is bigbluebutton/greenlight:latest which pulls from the main one.
Can you try any of the alternate images? bigbluebutton/greenlight:v2.12.6-alpine or bigbluebutton/greenlight:v2.12.6-amazonlinux
The various images yield different results, additionally depending on the host operating system (maybe Docker version). For both hosts described below I use a docker-compose.yml file, slightly customized to each host, but it's basically still the same as the one in this repository — I checked before running the tests. Each of the three image uses the same compose file.
Host one is a BigBlueButton single server machine, installed via the regular bbb-install.sh script — meaning it's Ubuntu 18.04 with Docker 20.10.17.
Two of the three relevant images do not work on this host:
- :negative_squared_cross_mark:
v2.12.6-amazonlinuxat7264f66ac95d, logs - :negative_squared_cross_mark:
v2.12.6-alpineat5d7beb2cd4be, logs - :heavy_check_mark:
v2atddc8ca9e5c5a
Host two is a separate server from a multi server environment with Scalelite. The host Greenlight is running on is Ubuntu 20.04 with Docker 19.03.08.
On this host neither of those three images work. The v2 image fails with the same error message that the author of this issue provided.
- :negative_squared_cross_mark:
v2.12.6-amazonlinuxat7264f66ac95d, logs - :negative_squared_cross_mark:
v2.12.6-alpineat5d7beb2cd4be, logs - :negative_squared_cross_mark:
v2atddc8ca9e5c5a, logs
as an update to this issue. I have noticed this issue only exists old Ubuntu 18 Nodes. After an upgrade and tests on Ubuntu 20 this issue no longer exists.
@mbunkus @LKLG @jplitza Are you guys also still running Ubuntu 18 😬 ?
We've migrated to BBB 2.5 on Ubuntu 20.04 in the meantime, with Docker image bigbluebutton/greenlight:v2 at 0325a3de11ec. This one works fine.
No version newer than 2.12.1 work for me on one host. On another host all versions work fine. Upgrading to Ubuntu 20.04 would mean a lot of work and I do not understand why this should be necessary.
same with 2.13.0. it is working on one server and on the other I have this error. And I have no f... clue why :( servers both running Ubuntu 20.04.1
okay I found out that I was using a version of docker that was too old. I used ubuntu docker version (docker server version 19.x) on one server and the official docker version on the other server (docker server version 20.x). I've added the official docker repo and did a dist-upgrade and then the new greenlight version started. Maybe something for the docs?
Same in Debian. Required the next major version of docker, fixed after upgrade and restarting docker.
Please note: Greenlight v3 has been released. With this new version, many of the issues and bugs that were present in v2 have been resolved.
As a result, we will no longer be providing updates or support for v2 (except for major security issues), and we will be closing any outstanding bug reports / feature requests related to v2. While we understand that some of you may still be using v2, we highly encourage you to upgrade to v3 to take advantage of the improved features and stability. If your request/bug still applies to v3, please open a new issue for it
