Skip to main content
In this guide, we’ll explore the rebase functionality offered by Buildpacks. Rebasing enables you to update the base image of an already built application without the need to rebuild all subsequent layers, resulting in a more efficient and faster update process.

​
How Rebasing Works

When using a traditional Dockerfile, the first layer of an image is typically the base image, followed by additional layers that include application dependencies and source code. Any change to the base image—such as an operating system update, applying a hotfix, addressing a security vulnerability, or adding new dependencies—requires rebuilding every layer above it. This process can be resource-intensive and inefficient. Buildpacks streamline this process. When you rebase an image with an updated base image, only the base layer is replaced, while the higher-level layers remain unchanged. This targeted replacement minimizes rebuild time and data transfer during the image update process.
The image compares the effects of rebasing with Dockerfiles and Buildpacks, showing that Dockerfiles cause all layers to change, while Buildpacks only change the specific layer, resulting in less data transfer and faster rebuilds.
Rebasing significantly improves your build performance by only updating the necessary layer. This makes it an ideal approach when you need to apply minor changes or security fixes.

​
Inspecting the Image

Before proceeding with a rebase operation, you can inspect the current image details using the Pack CLI. Run the following command:
A sample output might appear as follows:
In this output, note the Run Images field, which displays the current base image (run-base:v1).

​
Rebasing the Image

If you need to update the base image—whether to apply a hotfix, address security vulnerabilities, or add new dependencies—and have created an updated base image (for example, run-base:v2), you can perform a rebase with the following command:
This command substitutes the old base image (run-base:v1) with the new one (run-base:v2) without rebuilding the remaining layers.
Ensure that your updated base image has been thoroughly tested before performing the rebase in production. This helps avoid any unexpected issues.

​
Verifying the Rebase

After executing the rebase command, verify that the image now uses the updated base by inspecting it again:
An updated output should indicate the change as shown below:
This confirms that the new base image (run-base:v2) is now active, highlighting the efficiency and convenience of using Buildpacks for rebasing. For more detailed information on Buildpacks and image creation, consider reviewing these resources:

Watch Video