
While our Image Creator gives you the building blocks to add custom packages and environment variables to base Minimus images, file bundling adds flexibility by supporting additional use cases for further customization and consolidation of specific organizational files that are often bundled during separate build processes. These files can now be included automatically as part of Minimus image builds.
In this post, we’ll walk through how file bundling works, common use cases, and how to create file bundles inside Minimus Image Creator.
File bundling is designed for teams that need to include required files in their images without managing separate build logic or one-off Dockerfile changes. It helps standardize what goes into images across teams, environments, and entire fleets, while keeping builds consistent and easy to maintain.
With file bundling, you can:
File bundling in Minimus is designed to be simple and repeatable, and can be broken down into a few straightforward steps:
First, Navigate to Image Creator.
New bundles may be created prior to creating a private image by clicking “Manage Files”, or during the Image Creation Process by Selecting “Add File Bundle”.



After you create a new file bundle, you can upload files.
Certificates:

Other File Types:

You can also add an existing bundle during the Image Creation process:


After saving the bundles and launching the build, these file bundles will now automatically be included with each private image build and can be reused with other private images.

Extending the Minimus Image Creator functionality by bundling specific organizational certificate requirements and standard configuration files further allows engineering and application teams to adopt minimal package and CVE images while not compromising existing processes and requirements within existing image builds.
If you’re ready to simplify how required files are managed in your container images, head to Image Creator or get in touch to start using file bundles in your next private image build.