Before Black Duck began leveraging Docker, customers utilized the App Manager Install Method to deploy it. Black Duck now deploys as a set of containers, so customers need to install Docker to take advantage of updates to the application. By the end of this guide, you’ll have a basic understanding of how to migrate Black Duck to a containerized environment, as well as the benefits of using containers.
Docker is a packaging technology that allows you to bundle applications with its software dependencies—eliminating the need to configure infrastructure before deployment. It is built once and can run anywhere as a single unit. These units on their own are called images, but when they are being run as applications we call them containers.
The Docker architecture brings a number of significant improvements to Black Duck:
Black Duck is deployed as a set of Docker containers, which together comprise the application. Each container fulfills a different role. For example, the Web App container processes UI requests while the Solr container acts as the enterprise search platform component. A detailed description of each container’s role is available in the Black Duck Docker Install Guide on the Customer Success Community.
Please ensure that you meet all of the hardware and software requirements before getting started:
|Hardware (min. specs)||Software||Preferred Operating System|
|64-bit 5 core processor||Docker 17.03.x or Docker 17.06.x (CE or EE)||CentOS 7.3|
|20 GB of RAM||Orchestration tool such as Docker Swarm**, Docker Compose, Docker Run, or Kubernetes.||Ubuntu 16.04.x|
|250 GB of free space for the database and other Black Duck containers||For additional information on supported orchestration techniques, consult the Docker Installation Guide.||Oracle Enterprise Linux 7.3|
|Free space for database backups||Red Hat Enterprise Linux Server 7.3|
|SUSE Linux Enterprise Server 12.x|
|Linux Operating Systems that support Docker 17.03.x|
Note that the following steps depend on the operating system (OS). Also, while other methods are supported, this example uses the Docker Swarm tool to orchestrate the Black Duck container deployment and installation on a CentOS / Docker CE platform. To begin migrating to a containerized environment, we begin by installing Docker, which is comprised of five steps.
Step 1: Install required packages and set up the stable repository.
Step 2: Update the yum package index and install the latest version of Docker available.
Step 3: Verify installation with hello-world image, which runs a test image in a container. When it runs, Docker prints an informational message and then exits.
Post installation (optional)
Step 4: Manage Docker as a non-root user so you don’t have to issue a sudo command every time you want to run a Docker command. Start by creating a group called Docker.
Step 5: Configure Docker to automatically start when your system reboots.
We now begin moving your previous data to a Dockerized Black Duck. The Black Duck migration can be broken down into four major steps: 1) preserve configuration and open source data from the existing version of Black Duck before uninstalling it, 2) uninstall the old version of Black Duck, 3) obtain configuration and orchestration files for Dockerized Black Duck, and 4) restore your Black Duck data.
Step 1: If you want to retain your existing data on your open source components, you must first back up your database. Begin by logging onto the Black Duck server as a Black Duck user. After you’re logged on, dump your data to a compressed file with three commands:
Be sure to save the bds_hub.dump file onto another system or offline!
Step 2: Now that the database is backed up, we can uninstall the old Black Duck server. Start by navigating to the app manager bin directory and issue a command to stop all bin processes:
Now we are ready to uninstall the application:
Step 3: Download the orchestration and configuration files. You need these files to install Black Duck and launch the Docker images.
Unpack .tar file and configure Web server and, if needed, Proxy Server settings.
Now that we have the environment files, let’s configure the Web server and, if needed, proxy server settings.
Step 4: Now that the old version of Black Duck is uninstalled and you have the configuration and orchestration files, we can run the migration script to restore your open source data. This transfers the data from the existing database dump file. Begin by downloading and starting three of the containers and volumes needed to migrate the database:
Ignore the error messages if you have any, as they do not affect the data restoration. Now we are ready to run the migration script to restore your Black Duck data:
Now we are ready to install the Black Duck. Keep in mind that the following instructions are for those using the Docker Swarm orchestration tool. If you do not use Docker Swarm, please reference the Black Duck Docker Install Guide.
Step 1: Install the Dockerized Black Duck with the PostgreSQL database instance. Begin by initializing Docker Swarm, creating a single node swarm.
Now, install Black Duck with the PostSQL database instance; this creates all the containers that comprise the Hub.
Docker implementation of Black Duck enables scalability by allowing admins to choose the number of active job runner containers.
Step 1: Confirm Installation was successful by running the docker ps commands
As a Product Marketing/Business Rotational Program Associate at Synopsys, Charlie will rotate through the sales, marketing, sales operations, and finance departments four months at a time. He joined Black Duck Software in July, before Black Duck Software was acquired by Synopsys. During his time in sales and marketing, Charlie has researched and learned about the importance of open source risk management—especially pertaining to container security and secure DevOps practices. While in marketing, Charlie has been helping with the launch of OpsSight, a product designed for IT Operations and Infrastructure teams hoping to automate security practices in the production environment. He holds a B.A. in Political Economy from Bates College.