This is the second in our series of Docker blog posts. The first post, by James our CTO, focused on why UShareSoft for Docker software governance and transparency. In this post, we'll tell you exactly how to build a Docker base image using our tools.
By a base image, we mean a machine image containing just the necessary bits required to launch your container image. You can do this in two ways: using our UForgeNow SaaS platform, or using hammr, an open source tool for creating machine images for different environments from a single configuration file.
The goal of white box migration is to change the contents found during the scan of the live system prior to migration.
White box migration is not supported for Windows.
The goal of black box migration is to reproduce a near identical copy of the currently running workload. However, there will always be small differences between the two workloads after migration is complete.
To migrate a live workload to a new target environment, you first copy the uforge-scan binary to the target environment and launch the binary. This binary analyzes the live system and sends back a report, known as a scan back to UForge.
Give UShareSoft's Paul Laskin two and a half minutes of your time. You won't be disappointed. You'll find out how you can quickly and easily migrate workloads to cloud (or to any virtual or physical platform). You can also easily model your existing server as a template for extending and updating before migration, and conduct incremental scans for security and audit purposes.