VirtualBox logo
Run nearly any operating system on a single machine and to freely switch between OS instances running simultaneously

What is VirtualBox?

VirtualBox is a powerful x86 and AMD64/Intel64 virtualization product for enterprise as well as home use. Not only is VirtualBox an extremely feature rich, high performance product for enterprise customers, it is also the only professional solution that is freely available as Open Source Software under the terms of the GNU General Public License (GPL) version 2.
VirtualBox is a tool in the Virtualization Platform category of a tech stack.

Who uses VirtualBox?

Companies
718 companies use VirtualBox in their tech stacks, including Coursera, OpenTable, and Zapier.

Developers
928 developers use VirtualBox.

VirtualBox Integrations

Docker, Vagrant, Packer, Stackato, and AppScale are some of the popular tools that integrate with VirtualBox. Here's a list of all 9 tools that integrate with VirtualBox.

Why developers like VirtualBox?

Here’s a list of reasons why companies and developers use VirtualBox
VirtualBox Reviews

Here are some stack decisions, common use cases and reviews by companies and developers who chose VirtualBox in their tech stack.

Tymoteusz Paul
Tymoteusz Paul
Devops guy at X20X Development LTD · | 11 upvotes · 63.2K views
Amazon EC2
LXC
CircleCI
Docker
Git
Vault
Apache Maven
Slack
Jenkins
TeamCity
Logstash
Kibana
Elasticsearch
Ansible
VirtualBox
Vagrant

Often enough I have to explain my way of going about setting up a CI/CD pipeline with multiple deployment platforms. Since I am a bit tired of yapping the same every single time, I've decided to write it up and share with the world this way, and send people to read it instead ;). I will explain it on "live-example" of how the Rome got built, basing that current methodology exists only of readme.md and wishes of good luck (as it usually is ;)).

It always starts with an app, whatever it may be and reading the readmes available while Vagrant and VirtualBox is installing and updating. Following that is the first hurdle to go over - convert all the instruction/scripts into Ansible playbook(s), and only stopping when doing a clear vagrant up or vagrant reload we will have a fully working environment. As our Vagrant environment is now functional, it's time to break it! This is the moment to look for how things can be done better (too rigid/too lose versioning? Sloppy environment setup?) and replace them with the right way to do stuff, one that won't bite us in the backside. This is the point, and the best opportunity, to upcycle the existing way of doing dev environment to produce a proper, production-grade product.

I should probably digress here for a moment and explain why. I firmly believe that the way you deploy production is the same way you should deploy develop, shy of few debugging-friendly setting. This way you avoid the discrepancy between how production work vs how development works, which almost always causes major pains in the back of the neck, and with use of proper tools should mean no more work for the developers. That's why we start with Vagrant as developer boxes should be as easy as vagrant up, but the meat of our product lies in Ansible which will do meat of the work and can be applied to almost anything: AWS, bare metal, docker, LXC, in open net, behind vpn - you name it.

We must also give proper consideration to monitoring and logging hoovering at this point. My generic answer here is to grab Elasticsearch, Kibana, and Logstash. While for different use cases there may be better solutions, this one is well battle-tested, performs reasonably and is very easy to scale both vertically (within some limits) and horizontally. Logstash rules are easy to write and are well supported in maintenance through Ansible, which as I've mentioned earlier, are at the very core of things, and creating triggers/reports and alerts based on Elastic and Kibana is generally a breeze, including some quite complex aggregations.

If we are happy with the state of the Ansible it's time to move on and put all those roles and playbooks to work. Namely, we need something to manage our CI/CD pipelines. For me, the choice is obvious: TeamCity. It's modern, robust and unlike most of the light-weight alternatives, it's transparent. What I mean by that is that it doesn't tell you how to do things, doesn't limit your ways to deploy, or test, or package for that matter. Instead, it provides a developer-friendly and rich playground for your pipelines. You can do most the same with Jenkins, but it has a quite dated look and feel to it, while also missing some key functionality that must be brought in via plugins (like quality REST API which comes built-in with TeamCity). It also comes with all the common-handy plugins like Slack or Apache Maven integration.

The exact flow between CI and CD varies too greatly from one application to another to describe, so I will outline a few rules that guide me in it: 1. Make build steps as small as possible. This way when something breaks, we know exactly where, without needing to dig and root around. 2. All security credentials besides development environment must be sources from individual Vault instances. Keys to those containers should exist only on the CI/CD box and accessible by a few people (the less the better). This is pretty self-explanatory, as anything besides dev may contain sensitive data and, at times, be public-facing. Because of that appropriate security must be present. TeamCity shines in this department with excellent secrets-management. 3. Every part of the build chain shall consume and produce artifacts. If it creates nothing, it likely shouldn't be its own build. This way if any issue shows up with any environment or version, all developer has to do it is grab appropriate artifacts to reproduce the issue locally. 4. Deployment builds should be directly tied to specific Git branches/tags. This enables much easier tracking of what caused an issue, including automated identifying and tagging the author (nothing like automated regression testing!).

Speaking of deployments, I generally try to keep it simple but also with a close eye on the wallet. Because of that, I am more than happy with AWS or another cloud provider, but also constantly peeking at the loads and do we get the value of what we are paying for. Often enough the pattern of use is not constantly erratic, but rather has a firm baseline which could be migrated away from the cloud and into bare metal boxes. That is another part where this approach strongly triumphs over the common Docker and CircleCI setup, where you are very much tied in to use cloud providers and getting out is expensive. Here to embrace bare-metal hosting all you need is a help of some container-based self-hosting software, my personal preference is with Proxmox and LXC. Following that all you must write are ansible scripts to manage hardware of Proxmox, similar way as you do for Amazon EC2 (ansible supports both greatly) and you are good to go. One does not exclude another, quite the opposite, as they can live in great synergy and cut your costs dramatically (the heavier your base load, the bigger the savings) while providing production-grade resiliency.

See more
Marcel Kornegoor
Marcel Kornegoor
CTO at AT Computing · | 5 upvotes · 18.6K views
atAT Computing
Python
Chef
Puppet Labs
Ansible
Google Compute Engine
Kubernetes
Docker
GitHub
VirtualBox
Jenkins
Visual Studio Code
Fedora
Red Hat Enterprise Linux
Debian
Centos
Ubuntu
Linux
#ATComputing

Since #ATComputing is a vendor independent Linux and open source specialist, we do not have a favorite Linux distribution. We mainly use Ubuntu , Centos Debian , Red Hat Enterprise Linux and Fedora during our daily work. These are also the distributions we see most often used in our customers environments.

For our #ci/cd training, we use an open source pipeline that is build around Visual Studio Code , Jenkins , VirtualBox , GitHub , Docker Kubernetes and Google Compute Engine.

For #ServerConfigurationAndAutomation, we have embraced and contributed to Ansible mainly because it is not only flexible and powerful, but also straightforward and easier to learn than some other (open source) solutions. On the other hand: we are not affraid of Puppet Labs and Chef either.

Currently, our most popular #programming #Language course is Python . The reason Python is so popular has to do with it's versatility, but also with its low complexity. This helps sysadmins to write scripts or simple programs to make their job less repetitive and automating things more fun. Python is also widely used to communicate with (REST) API's and for data analysis.

See more
Marc Lachance
Marc Lachance
Senior Front End Engineer at Myra Security GmbH · | 4 upvotes · 1K views
VirtualBox

I use VirtualBox over other VM tools because of familiarity, and because the slowness actually is good for creating pain points for me as a developer long before the end user will see them. But really, I use it because it's free, I am not in the mood to learn something new that I would also end up having to pay money for.

See more
Josh Frye
Josh Frye
Senior Software Engineer at StackShare · | 3 upvotes · 7.1K views
Docker
VirtualBox
Packer
Ubuntu
Vagrant
#VirtualizationPlatform
#VirtualMachine
#Devops

I use Vagrant to build Railsbox. I base the final image off of another Vagrant base image Ubuntu to speed up build times. In the past I've used Packer to build the image, but installing Ubuntu from scratch takes too much time. Using a base VirtualBox image allows me to compose a Vagrantfile similar to Docker's "FROM image" command #devops #VirtualMachine #VirtualizationPlatform

See more
Docker
Cloud9 IDE
VirtualBox
Ubuntu
Windows

I have long sought after the perfect local development environment for developing JavaScript applications, and after having tried several different complete setups, I finally ended up choosing to develop on a Windows host with a Ubuntu virtual machine running with VirtualBox. When the VM comes up, it automatically brings up Cloud9 IDE, which provides a great JavaScript editor, terminal access from your browser, as well as the ability to work remotely by choice and still have the exact same development environment, all served up in a browser. This helps keep the host system clean, and using Docker in the virtual machine helps keep the VM clean as well as it is the only dependency that is required to be installed to run applications.

See more
Wesly Nouse
Wesly Nouse
Owner at Absolum · | 3 upvotes · 400 views
atAbsolum
Kubernetes
Docker
VirtualBox

We use VirtualBox to test and create virtual environments, be it a Docker setup, a Kubernetes cluster, a Virtual network or just a normal vm. VirtualBox is the best solution for us because it's free and it works the same as it's competitors.

See more

VirtualBox's features

  • Portability
  • No hardware virtualization required
  • Guest Additions: shared folders, seamless windows, 3D virtualization
  • Great hardware support
  • Multigeneration branched snapshots
  • VM groups
  • Clean architecture
  • unprecedented modularity
  • Remote machine display

VirtualBox Alternatives & Comparisons

What are some alternatives to VirtualBox?
Docker
Docker is an open-source project to easily create lightweight, portable, self-sufficient containers from any application. The same container that a developer builds and tests on a laptop can run at scale, in production, on VMs, bare metal, OpenStack clusters, public clouds and more.
KVM
KVM (for Kernel-based Virtual Machine) is a full virtualization solution for Linux on x86 hardware containing virtualization extensions (Intel VT or AMD-V).
Vagrant
Vagrant provides the framework and configuration format to create and manage complete portable development environments. These development environments can live on your computer or in the cloud, and are portable between Windows, Mac OS X, and Linux.
Hyper
Hyper.sh is a secure container hosting service. What makes it different from AWS (Amazon Web Services) is that you don't start servers, but start docker images directly from Docker Hub or other registries.
VMware vSphere
vSphere is the world’s leading server virtualization platform. Run fewer servers and reduce capital and operating costs using VMware vSphere to build a cloud computing infrastructure.
See all alternatives

VirtualBox's Stats

- No public GitHub repository available -