Please follow the instructions relative to your Operating System.
This installer will take care of all the BDBM dependencies. Once installed, a BDBM icon will be available in your user interface.
BDBM requires a 64-bit installation regardless of your Linux version. Additionally, your kernel must be 3.10 at minimum. To check your current kernel version, open a terminal and use uname -r to display your kernel version.
To download and install BDBM, open a terminal and execute this command as root:
bash -c "$(wget -qO- http://static.sing-group.org/BDBM/docker/bdbm-docker.sh)"
Or with sudo:
sudo bash -c "$(wget -qO- http://static.sing-group.org/BDBM/docker/bdbm-docker.sh)"
To be able to share files with BDBM, you have to select a path.
The installer will ask you for a path, by default
/home will be selected
as shared directory.
BDBM needs a path to store its repository.
The installer will ask you for a path to store BDBM repository, by default
will be selected as repository path.
You can uninstall the main dependencies separately. These are the packages that BDBM installs if they are not already available in your system:
If you want to remove all the docker images and BDBM configuration also, issue the following command. This action can't be undone.
rm -rf /var/lib/docker /opt/BDBM
To install BDBM, your machine must have a 64-bit operating system running Windows 7 or higher. Additionally, you must make sure that virtualization is enabled on your machine.
If virtualization is not enabled on your system, follow the manufacturer’s instructions for enabling it.
Depending on your system configuration you may need to pause the antivirus software to install correctly this software.
Download BDBM installer from here.
Setup will now install BDBM and its dependencies. It can take several minutes to complete.
Depending on the configuration of your Operating System, you may need to accept some alerts and the installation of aditional drivers.
BDBM is now ready to start working. You can open it from the BDBM icon on the desktop and also from the Start Menu folder.
The first time it will take a while to start because it has to download the last version available of the BDBM docker image (~600MB) and execute it.
You need to allow the creation of the base repository for BDBM on the first time.
To install BDBM, your Mac must be running OS X 10.8 "Mountain Lion" or newer.
Download BDBM installer package from here.
Open BDBM application from the Applications folder, it will open a Terminal window where you can see the progress of the configuration and the download of the docker image (~600MB).
The first time you need to allow the creation of the base repository for BDBM.
After the creation of the base repository, the application will be ready to use.
By default, BDBM base repository will be stored in ~/bdbmrepo and any file inside /Users will be available to BDBM.
You can uninstall BDBM and the main dependencies separately: VirtualBox, Xpra and Docker Toolbox.
To uninstall them just drag the app from the Applications folder to the Trash.
"bdbm-installer.pkg can't be opened because it is from an unidentified
Your security preferences allow installation of only apps from the Mac App Store and identified developers.
In this case, you need to allow the execution of the installer in the system settings: "Security & Privacy". There, click the button "Open Anyway" to launch the installer, or allow apps downloaded from Anywhere.
Error checking TLS connection: Error getting driver URL: Something went wrong running an SSH command!
This error may happen the first time BDBM is started and is related to the network configuration of VirtualBox. To fix it, it is necessary to check the network configuration in VirtualBox.
Open VirtualBox and go to menu File > Preferences. Then select Network section and go to Host-only Networks tab. Select "VirtualBox Host-Only Ethernet Adapter #2" and edit its configuration. On the DHCP Server tab, DHCP service must be enabled with the following configuration:
In the Mac OSX version of BDBM there are some incompatibilities with several keyboard layouts like ES-ISO. Some keys may print spaces instead of the character associated to the key. The current workaround is to use another keyboard layout like ES or EN-US.
Errors ocurred. See the logfile xpra.exe.log for details
This error may occur because there are some permission problems in the installation path of Xpra on Windows 10.
The current workaround is to use the shortcut BDBM Viewer available in the Start Menu.
docker: Error response from daemon: client is newer than server (client API
version: 1.22, server API version: 1.21).
See 'docker run --help'.
This error may occur when updating BDBM. In this case, you need to upgrade your docker image using the following command:
Once it finishes the upgrade, you need to restart BDBM virtual machine from VirtualBox or reboot your system.
Errors occurred: See the logfile 'C:\Program Files (x86)\Xpra\xpra.exe.log' for details
This error may happen every time BDBM is started in Windows and it is related to a permissions problem when starting the Xpra client.
The current workaround is to use the BDBM Viewer shortcut available in the folder BDBM under All programs.
BDBM needs EMBOSS, bedtools, and NCBI's BLAST, Splign, Compart, ProSplign and ProCompart applications in order to work, so you will have to install them before start with this installation process.
You can find the installation files and instructions of this programs in their respective web pages:
On some Linux-based systems there is no libpcre.so.0 file, a library that is required
by Splign. This can be, however, solved by creating a symlink to libpcre.so.3. To
solve this issue quickly, simply go to the directory that contains the libpcre.so.3
file (usually /usr/lib/ or /usr/x86_64-linux-gnu/) and run the command
libpcre.so.3 libpcre.so.0 (it may require root privileges).
ProSplign depends on the libdb-4.6.so library that it is not usually present in recent
Linux distributions. To solve this problem you can link this library to a more recent
version that is more common. Specifically, you can do this with the command
/usr/lib/x86_64-linux-gnu/libdb-5.3.so /usr/lib/x86_64-linux-gnu/libdb-4.6.so (it may
require root privileges)
ProSplign also requires library libcurl. If it is not present in your Linux
distribution, please install it using your package manager, for example:
apt-get install libcurl3 in Ubuntu/Debian or
yum install libcurl
Download your BDBM copy from here (3.9MB) and go to step 2.
Decompress the downloaded file (you will need a ZIP decompressor).
Once decompressed you should have a directory structure like seen in Figure 1.
Now you are ready to launch BDBM.
On a Linux-based system, double click on the
run.sh file. This will launch the
run-validate.sh option is used, a verification of the suitability of the FASTA
files present in the
/fasta/proteins folders that are located in
the specified repository folder (see below) will be performed. For very large files this
takes a long time. Therefore, this option is intended to be used as a debugging tool.
When running BDBM for the first time the user must indicate the location of the BLAST,
EMBOSS, Splign, Compart, ProSplign, ProCompart and bedtools utilities, as well the location
of the repository files. If needed, this can be changed later on.
You need VirtualBox to use the BDBM Virtual Machine. You can find the installation files and instructions of this programs in VirtualBox.org
Download your BDBM Virtual Machine copy from here (2GB) and go to step 2.
Decompress the downloaded file (you will need a ZIP decompressor).
Once decompressed you should have a file called
BDBM-ADOPS.vdi with is
the virtual machine hard disk.
Now you are ready to use the BDBM Virtual Machine.
Open VirtualBox and click on the New button. Give a name to your virtual disk and under Operating system choose Linux (the Ubuntu version will be automatically selected). Click on the Next button.
Choose the amount of RAM memory to be allocated to the virtual disk. Choose at least 2GB. Click on the Next button.
Choose the Use an existing virtual hard drive file option and select the
location of the
BDBM-ADOPS.vdi file you extracted (by clicking on the icon that
looks like a folder). Click on the Open, Next, and then
Click on the Start button to run the BDBM virtual machine.
You are now running Ubuntu as a bdbm-adops user. BDBM is installed under the /opt directory, but shortcuts to launch BDBM and ADOPS are available on the desktop left sidebar. Click on top of the BDBM icon to run it.
The Ubuntu virtual disk you just installed is fully functional, including the internet connection, and thus you can download the data from your preferred databases using the Ubuntu virtual disk. Nevertheless, it is possible to get access to the files on the host computer from this virtual disk. If you are using an USB pen, insert the device afterstarting the Ubuntu virtual disk only. Then go to devices (look at the top frame) and select USB devices. Click on top of the name of your USB pen. Your USB pen will be accessible (it may take up to 20 seconds to capture the USB port) under Places.
Although the virtual machine will automatically log in as the
bdbm-adops user when
you run it, if you want to do any operation that requires administrator level permission you
will be prompted to provide a password. In that case, the password that you have to introduce is:
You can download BDBM source from this GitHub repository or you can clone BDBM project using:
git clone https://github.com/sing-group/BDBM.git