I have been looking around for the installation steps for BigBlueButton 0.9 in CentOS version 6+ without any results. I have only been provided installation steps for BigBlueButton 0.6. Any directions where I can get the installation details for BBB 0.9 in CentOS 6+?
so far i have not seen BBB installation steps for CentOS however, you can surely able to install Docker on CentOS for BBB.
You easily install bigbluebbutton on centos by simply installing all the open source components separately first.
You can find the open source components here,http://bigbluebutton.org/components/
After that, install the webapps to bigbluebutton web and bigbluebutton app.
Configure the bigbluebutton.propreties in the web, create the ruby god conf file to allow record and play back, create the needed directories and setup the nginx config.
All these tasks are simple by them selves, but this process will take you a few days.
It took me a 2 days to install 0.81 on centos, so i can definitely guarantee that it is possible and doable without any extra needed applications.
Related
I'm trying to work on a project, and the setup steps begin like this:
Clone the repo
Set up Docker
Run make
Being a Windows user, I installed Docker for Windows, and it installed WSL2 to get all the Linux stuff set up. But when I went to run make from the WSL shell, it couldn't find it. So I tried to get make from apt-get... and that wasn't there either!
It would appear that my WSL2 install is broken. Unfortunately, Googling for it hasn't turned up much of use. So how do I obtain apt for WSL so that I can build my toolchain?
Something similar happened to me: I installed Docker Desktop in Windows some months ago and it configured WSL to run behind it. However, it was WSL version 1 instead of version 2, and it did not install any Linux distro, since both apps run on top of WSL.
So please, go through the tutorial on the manual installation of WSL to check if all the steps are actually configured.
Before that, you can already check what version of WSL you have installed and its state, by running, in CMD or PowerShell:
wsl -l -v
After you set WSL v2 as your default version (Step 5 of the tutorial), you can make sure that Docker Desktop uses it. For that, check this link on the Docker Desktop WSL 2 backend, more specifically the Install section.
Regarding the make part of your setup, I believe that you can do that in a system of your preference. If you want to do that on WSL, I recommend you install Ubuntu running over your WSL (Step 6 of the tutorial).
Once you installed Ubuntu or other distro, you can run it as any other app. There, you can manage your apt, make and other installations right as in Linux :)
I want to install Discourse on my server and it needs docker to work. I already have WHM with Cpanel installed on Centos 6 dedicated server, should I install docker or it will create problems?
If it's okay to install Docker on my server then should I install it on a single site or on the whole server via root?, I need to run 2 copies on discourse on two different domains.
Also, let me know if there will be any performance issue after installing Discourse.
Thanks
Haven't found anyone who has answered this question. I too am wondering the same.
However, I'm going to go ahead and try it.
Steps I have taken so far:
Create a Centos 7 fresh install server (as I have had issues with docker setups on Centos 6 previously and was told repeatedly Centos 7 fixes those issues).
Manually (via command line) setup WHM.
Submit ticket to have cPanel license assigned to our new server (I was told this was not supported, only to correct the staff telling me so with reference to another ticket telling me I have to request they assign a cpanel license to my Centos 7 setup, as vultr.com does not as of yet have a one click app install for WHM/Cpanel on Centos 7.) Cpanel license was then assigned to my Centos 7 server after correcting staff member.
After all WHM/Cpanel setup completed and working like a charm (including installing CSF for WHM)... I took a snapshot of the server so I can restore it if all else fails.
Waiting for snapshot to finish, reading up on requirements for docker and discourse, then will attempt to set the same up on the same server...
Server Specs (Vultr.com):
4 vCore
RAM: 8192 MB
Storage: 100 GB SSD
Bandwidth: 4000 GB (0%)
OS: CentOS 7 x64
I will return and relate my experience and steps taken to have both running.
FYI. I am not a server admin whatsoever, but a noob who can learn tech stuff enough to get by. I have setup docker droplets on digital ocean successfully a few times, so I hope I can combine the two to see if I can get both working on the same instance rather than pay for two separate servers for both Discourse/Docker and WHM/Cpanel.
I followed this tutorial:
link
I Skipped Setup Swap File as my server has enough ram.
I also made sure to disable SELinux.
nano /etc/sysconfig/selinux (disabled, then reboot server)
sestatus
Just run this command:
curl -fsSL https://get.docker.com/ | bash
and be happy!
We are running docker 1.7.1, build 786b29d on RHEL 6.7. Recently we have had multiple times when the docker daemon locked up and we had to reboot the machine to get it back.
A typical scenario is that a container that has been running fine for weeks suddenly starts throwing errors. Sometime we can restart the container and all is well. But other times all docker commands will hang, and restarting the daemon fails, and I see this in a ps:
4 Z root 4895 1 0 80 0 - 0 exit Aug23 ? 00:01:24 [docker]
Looking in the system log I've seen this:
device-mapper: ioctl: unable to remove open device docker-253:6-1048578-317bb6ad40cded3fbfd752d95551861c2e4ef08dffc1186853fea0e85da6b12b
INFO: task docker:16676 blocked for more than 120 seconds.
Not tainted 2.6.32-573.12.1.el6.x86_64 #1
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
docker D 000000000000000b 0 16676 1 0x00000080
ffff88035ef13ea8 0000000000000082 ffff88035ef13e70 ffff88035ef13e6c
ffff88035ef13e28 ffff88062fc29a00 0000376c85170937 ffff8800283759c0
0000000000000400 00000001039d40c7 ffff8803000445f8 ffff88035ef13fd8
Call Trace:
[] _mutexlock_slowpath+0x96/0x210
[] ? wake_up_process+0x15/0x20
[] mutex_lock+0x2b/0x50
[] sync_filesystems+0x26/0x150
[] sys_sync+0x17/0x40
[] system_call_fastpath+0x16/0x1b
The latest docker version is 1.12.1 and we are on 1.7.1. Can or should I install a new version? 1.7.1 is the version yum installs. If I did want a new version how would I install that (sorry if that is a dumb question, I am not a sys admin).
Googling, I found on this on a Red Hat site "Red Hat does not recommend running any version of Docker on any RHEL 6 releases." We have been running docker on RHEL 6 for a few years, so this confuses me. Upgrading to RHEL 7 is not really an option for us right now.
Can anyone shed any light on these issue? We need docker to work reliably without having to reboot often.
Docker 1.7.1 is really old by today's standards. There have been hundreds of bugs fixed, enhancements to driver stacks, security patches, and valuable features added in the versions since. It looks like you're having a issue with your storage stack, and there is a good chance this is fixed in a newer version.
Docker has stated that default versions in package management systems like yum and apt can be way out of date, and that you should use their repo. The best way to do this is add their Yum repo information to your system so you can install it like other packages. The instructions are here: Installation on Red Hat Enterprise Linux.
Note: This will allow you to install Docker, and the service will be called docker, but the package is docker-engine. This has confused some people in the past.
yum install docker-engine
Docker has also provided a script that does this to make things easier (run as admin/root):
curl -fsSL https://get.docker.com/ | sh
Don't use a RHEL6 based system.
RHEL6 uses a 2.6 kernel with backported fixes to keep Docker working. Docker would normally require a 3.10+ kernel. Docker dropped support for RHEL6 from v1.8 on so it's unlikely there will be any more packages for it.
If you must use RHEL6, don't use the default loopback devicemapper for storage. Setup an LVM thin pool for Docker to use.
I have downloaded docker binary version 1.8.2 and copied that to my backup server (centos server) which doesn't have internet connectivity. I have marked this as executable and started the docker daemon as mentioned in [https://docs.docker.com/engine/installation/binaries/][1]. But it doesn't seem to get installed as a docker service. For all the commands, I have to execute as sudo ./docker-1.8.2 {command}. Is there a way to install docker-engine as a service? Currently sudo docker version shows command not found. I'm a newbie to docker setup. Please advise.
Why not download the rpm package (there are also centos 6 packages), copy to USB stick and then to your server and simply install it with rpm command and that's it. That way you'd get the same installation as if you were to run yum.
Of course you may have some dependencies missing, but you could download all of these as well.
Firstly, if you're downloading bare binaries on an enterprise linux, you're probably doing things in a very bad way. Immediately, you're breaking updates and consistency, and leaving your system in a risky, messy state.
Try using yumdownloader --resolve to get the docker installable and anything it needs.
A better option may be to mirror the installation artifacts, and grab it from the local mirror, but that's beyond the scope if you don't do this already.
I want to install docker 1.3.1 on my centos 6.5 environment but I have no idea how to find it in the epel. I'm quite new to docker. Can anyone help me out? Thanks
Clearly stated in the Docker documentation:
Docker runs on CentOS 7.X.
CentOS 6.5 is not CentOS 7.X. Docker is not available for your old operating system.
Furthermore, you didn't give any details about your computer, but you should remain aware that Docker only works on 64-bit systems.
By the way, you should take better care of your computer; in CentOS, the minor version number is updated automatically by the package manager. So the fact that you are two versions behind (CentOS 6 is currently on 6.7) indicates that you are not performing updates to your packages, and could have various security vulnerabilities. You should update your system regularly, by simply running yum update.