Bahmni Virtual Box


Whether you use Windows, Linux or Mac, you can use this process to have Bahmni running on your machine for Testing or Development. Note that it is NOT recommended to use this in production. The idea is to download the Bahmni Virtual (Vagrant) Box which is pre-installed with CentOS, and all softwares. To make the vagrant box run on your machine you will need Virtual Box, Vagrant and GIT installed (See steps below). Once you have this Vagrant box running, you can then make changes to file in the box, and see them reflect immediately. If you still wish to go ahead, and make code changes, and deploy them - then development setup will be needed, so that you can modify files in your base OS, and run them inside the Vagrant box after recompilation. 

Understanding Vagrant

For development purposes we use Vagrant and Virtual Box. The vagrant box for v0.92 Bahmni should be Centos 7.6. To understand Vagrant better, you can read the following links:

  1. Why Vagrant?
  2. Difference between Vagrant boxes/VMs.
  3. Understanding the Vagrantfile

  4. Quick Intro to Vagrant 

Deployment Architecture

Please read the document: High Level Deployment Architecture of Bahmni, to understand the major components that are present in the Virtual Box for Bahmni

The latest version of Bahmni is v0.93

Apple M1 Chips

Vagrant/Virtual box are NOT supported on Apple M1 Silicon processors. See this discussion for options:

On this page

Perform the following steps to get Bahmni VM setup on your computer

Video Screencast for Windows Installation

You can watch a video on how to setup Bahmni with Virtual Box / Vagrant here: (Youtube Video). This video is created for Windows, but the steps are similar for Linux and Mac systems too.

Copying from another Bahmni Vagrant Box

If you have another Bahmni Vagrant box (in your team or another location on network) then you can save time by not downloading the vagrant. See steps given in the section Transferring your Vagrant box to another machine

FOSS development on Un*x platforms

You may encounter issues while setting up VirtualBox on Windows and we encourage you to do your Bahmni related FOSS development on Un*x platforms.

Virtualbox set up on Ubuntu

You may encounter issues while setting up Virtualbox on Ubuntu 16.04 with a dual boot Windows 10. Please read this article and discussion on before installing virtualbox.

Step 1: Install Git, Virtual Box and Vagrant on your computer

There is a known issue with Vagrant on Windows10. Please read this discussion to understand what you need to do: before installing vagrant.

For users running Windows 7/8, you may be 

Step 2: Create a folder bahmni where you would like all project related files to be present
cd /Projects
mkdir bahmni
Step 3: Clone the following projects from Github inside the newly created folder bahmni
cd bahmni
git clone
Step 4: From within directory bahmni-vagrant execute "vagrant up" command

This command will download a CentOS Vagrant Box from the internet, and install it on your machine ('vagrant box list' command shows a list of locally installed boxes). 

cd bahmni-vagrant

# Make sure that the command prompt is running "As Administrator" otherwise the next command vagrant up will hang on 'Clearing any previously set network interfaces'. 
#This command will download the Vagrant box from Atlas first time. Next time onwards, the already downloaded vagrant box will be used.
# The download box size is about 2.5 GB. Please ensure you have a good and stable internet connection to download the box. Usually vagrant will continue download from where it got disconnected.

vagrant up

Vagrant Errors

 If the vagrant up command throws some error, please refer to the following page for possible error resolution: Vagrant and VirtualBox tips

If download of the box fails in the step above, and you wish to directly download the box using a downloader utility, then you can try the steps documented here: Direct Download of Vagrant Box.

If any service isn't running, then maybe you won't see the login screen. Please start that service, and then check. For details on all services in Bahmni, please refer to this document: Install Bahmni on CentOS (Services)

Configure Valid SSL Certificates

When you first access the web application your browser may show a warning about an invalid security certificate, and that your connection is not secure / private. If you are testing or evaluating Bahmni you may get around this by using a self-signed certificate or adding a security exception/choosing to proceed to the site (this varies across web browsers). Otherwise please read the following document for recommended guidelines on generating SSL certificates for securing Bahmni access over HTTPS connections: Configure Valid SSL Certificates. In Firefox browser, the Advanced link will allow you to continue forward. In Chrome you may need to run the browser with temporarily disable warning (read this). For security, please don't disable this on browser permanently.

Bahmni Home Landing Pagehttps://

Bahmni EMR & Clinical UI

Lab System (OpenELIS)

 ERP System (Odoo) - Billing and Inventoryhttp://


Note: On v0.91 this would go to OpenERP whose credentials are: admin/password (Choose Database "openerp" in top right corner).

OpenMRS - Configurationhttps://

Increase RAM for VM

The current "Vagrantfile" is configured with only 3GB RAM. To make all services run well, usually > 4GB is needed. If your host machine has more RAM, please consider increasing the RAM allocated to your Vagrant box. For doing that, please edit this line in your vagrant file: Change the value of "--memory" 3092 to a higher value (in KB). (See System Requirements#Testinstallations)

Step 6: To halt the VM, you can use the "vagrant halt" command
cd bahmni-vagrant
vagrant halt 
# Use 'vagrant up' next time, to restart the box.

Working Inside the Bahmni Vagrant Box

Working Inside the Bahmni Vagrant Box

Once you have vagrant running successfully, you can ssh into it, and browse the following directories.

Please refer to this document, to understand the various folders in a typical Bahmni installation on CentOS.

#ssh into the box
vagrant ssh
# The bahmni code folder of host machine is mapped to /bahmni of the VM
cd /bahmni
# For httpd server (where the EMR UI runs from): 
cd /var/www/

Starting / Stopping your Vagrant Box

cd bahmni-vagrant
# Stops your vagrant box (and remembers all file system changes)
vagrant halt
# Brings your vagrant back on (if you did 'vagrant halt' earlier to stop)
vagrant up
# Destroy and free up space - Any changes you made inside the vagrant will also be lost
vagrant destroy
# Creates and starts a fresh box (won't download anything) from the originally downloaded Bahmni box template
vagrant up

Updating your Vagrant Box to the Latest Version

If you already have a Bahmni vagrant box on your machine, but would like to update to the latest published box, please perform the following steps. 

cd bahmni-vagrant
vagrant halt
# See which versions of Bahmni vagrant box are installed on the machine
vagrant box list
# Warning!! This will destroy any changes you made in the vagrant box
vagrant destroy 
# (Optional Step) Delete the box template of a specific version if you don't want it, or you want to download it again
vagrant box remove bahmni-team/bahmni --box-version="0.81"

# Will search and download the latest Bahmni vagrant box (about 1.5GB +)
vagrant box update 

# You new box should come up now
vagrant up 

Transferring your Vagrant box to another machine

If you wish to transfer the same vagrant box from your machine to another machine, you can also do that. This has the following advantages: 

  1. Any data you setup in your vagrant box will also be available to the other box/machine. 
  2. If the other machine doesn't have fast internet access, then also you can perform this machine to machine box transfer, and save on bandwidth.
  3. Its quicker than downloading the whole box!

Steps to perform: 

Reference document:

  1. Create Reference Box: Create a new vagrant box that has everything from your box packaged into it using the following commands: 

    # Execute these commands from the same folder where your vagrant box is kept.
    # Halt vagrant
    vagrant halt
    # Create a new .box. This will create a file
    vagrant package
  2. Use Box on Target Machine: On the new machine, perform the following steps: 
    1. Create a new folder, say: "D:/my-bahmni-vagrant"
    2. Copy over the "" file and "Vagrantfile" from your machine into the above folder.
    3. Edit the Vagrantfile and do the following: 

      # Change this value as below = "my-bahmni-box"
      # Add this line to point the url to the
      config.vm.box_url = "file:///d:/my-bahmni-vagrant/"
    4. Save the Vagrant file and execute "vagrant up" command.

Now the vagrant box on the new machine should be up. You can repeat step 2 on other machines, now that you have a as reference for others.

Setting up an AWS Machine using your Vagrant / VM Box Image

Read this document: Exporting your VM to AWS

Direct Download of Vagrant Box

If you are unable to download the box using the "vagrant up" command, you can choose to download it via some other downloader utility directly using this link: 




v 0.92:

v 0.91:

v 0.90:

v 0.89:

v 0.88: 

v 0.87:

v 0.86:

v 0.85:

v 0.83:

After download, rename the box to "". Place the box in your "bahmni-vagrant" folder, and edit the Vagrant file as below: 

Vagrantfile changes
# Change this value as below = "my-bahmni-box"
# Add this line to point the url to the
config.vm.box_url = "file:///d:/my-bahmni-vagrant/"

Now save the Vagrantfile. And then execute the "vagrant up" command. 

From Bahmni v0.89, the Bahmni virtualbox comes with oh-my-zsh shell, Git installed. This will helpful for the newbies to navigate inside vagrant box. For details check this PR.

The Bahmni documentation is licensed under Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0)