Bacula Enterprise Edition is available on Docker.

Using Docker to create and manage containers can simplify the creation of highly distributed systems by allowing multiple applications, worker tasks and other processes to run autonomously on a single physical machine or across multiple virtual machines. This allows the deployment of nodes to be performed as the resources become available or when more nodes are needed, allowing a platform as a service (PaaS)-style of deployment and scaling for systems. Docker also simplifies the creation and operation of task or workload queues and other distributed systems

By using containers, resources can be isolated, services restricted, and processes provisioned to have an almost completely private view of the operating system with their own process ID space, file system structure, and network interfaces. Multiple containers share the same kernel, but each container can be constrained to only use a defined amount of resources such as CPU, memory and I/O.

It is useful to know that two key concepts that are used often are “images” and “containers”. Images are the “objects” that are distributed and contain the software. The container is what is actually executed from the image.


Deployment and upgrade are integral parts of the Docker workflow



Zero maintenance

Bacula System’s partner RedCoolBeans will provide security and reliability updates for the base-software inside the image, as well as for Bacula. When there are security or reliability updates available, customers will be notified that new images are available for download.

Deployment and upgrade are integral parts of the Docker workflow. Therefore it’s extremely fast to deploy a new container or to perform an upgrade of the images. For upgrading the Bacula database schema, the Bacula Enterprise upgrade guide needs to be consulted.

Platform can be changed

Customers are not locked to one particular platform, whether it’s physical or virtual. The Docker images can be deployed on a new machine or cloud provider in seconds. This also increases the reliability as an administrator doesn’t have to re-install a machine and configure Bacula again in case of hardware failure. The container is launched elsewhere and the installation is whole again.

Virtually no learning curve

Backup/system administrators no longer have to maintain and administer the whole underlying operating system of the system where Bacula runs. The only thing that has to be managed is the Bacula configuration, and not Bacula itself, or RedHat, or Debian, or the database, etc.

For those not yet familiar with Bacula, the images provide a great and low-barrier way to get started with an enterprise backup solution like Bacula. It’s basically “plug and play”.


            For organizations that do not have any Docker experience yet, RedCoolBeans will be there to assist you every step along the way. Docker is an exciting new paradigm in computing and the benefits of getting ahead of the crowd with containerized and service-oriented architectures are plenty.

Easy migration from standard Bacula to Dockerized Bacula EE

An easy migration is possible to upgrade from an existing Bacula Enterprise or Open Source setup to the Dockerized setup. You only have to copy your existing configuration to the Docker host and load your database and you’re ready.

Upgrade path to run your Bacula in the Cloud

            As many cloud providers offer the option to run Docker container’s the RedCoolBeans Bacula images are ideal for upgrading your infrastructure to a private, public or hybrid cloud.

How do you use it?

Installed from protected Docker Hub Account

The images are distributed by a protected account through the Docker Hub, the Docker registry operated by Docker Inc.

In your existing Docker environment

The images can be deployed into an existing Docker environment just as well as they can be deployed into a brand new setup. As long as images can be pulled, you’re ready to go!

After subscription is paid

After the subscription purchase has been completed and verified, the images can be pulled.

Updates will be pushed to Docker Hub platform where they can be retrieved automatically

Any updates to the images will be pushed to the Hub and can be downloaded automatically. By using Docker tags we’ll ensure you’ll get exactly the right Bacula version you need without sudden upgrades.

User friendly configuration can be edited without to rebuilding the container

            When making a configuration change to Bacula there’s no need to rebuild a container. In fact, you’ll never have to rebuild anything! Depending on the type of change Bacula can reload the configuration itself, and in the worst case you’ll just restart the container and be back online in seconds.

Runs everywhere

With traditional applications you’re limited to which platform your vendor recommends. These images can be deployed on a Docker host running on KVM, bare metal or different fully virtualized environment. And the images can be deployed straight to AWS, VMware, and many other cloud providers which support Docker.


Read-only containers

Docker is designed in such a way that containers cannot write outside of their private filesystems, unless explicitly configured otherwise. This effectively means that containers are read-only from a host point-of-view.

Restricted host access

Due to the fact that Bacula and PostgreSQL run inside of a container, these processes are unaware of any other process running on the host. They are separated by various layers of security. On top of that the containers only expose network ports that are strictly needed, so no more SSH, Telnet, or any other port other than the bare minimum that needed for a container to perform it’s duty.

Minimal footprint of installed packages

No unneeded packages are installed inside the images, and no services are running other than the Bacula processes. This dramatically reduces the attack surface and tools available to a potential intruder.

Fast security response (24h) after announcement

We strive to provide updated images for all supported versions within 24 hours of the announcement of a security or reliability update by Bacula Systems or a the vendor of related components such as PostgreSQL.

Separate Containers

The Bacula stack runs in three separate containers, each for it’s own service: PostgreSQL, Bacula Director and Bacula Storage Daemon. The PostgreSQL database comes pre-tuned according to the Bacula recommendations and allows to be tuned even further based on your particular needs and requirements.


The intended sales process is that a customer purchases a subscription to the Docker images. These subscription are sold by existing partners of Bacula Systems, or directly through RedCoolBeans. These subscriptions are valid for one year and not limited to any number of clients connecting to the services in the images. The subscription fee does not include the Bacula Enterprise license.

Support for the Docker image with Bacula is included. This means that RedCoolBeans provides support for everything Docker related, and Bacula Systems supports their own software.


There are free Docker images available of Bacula Open Source on . These images are not configured to the same level of security as the enterprise images and lack various features and pre-tuned parameters. They are provided free of charge and do not come with commercial support.


Further help: