Minimus Reviews & Product Details

Consistency across environments has been a major improvement for us. We run these images across multiple Kubernetes clusters, and everything now feels much more standardized from one place to the next. The images are lightweight, which translates into faster pull times and more efficient resource usage on our nodes. On top of that, they provide a solid, hardened baseline that all teams can follow, and that kind of uniformity was something we were missing before. Review collected by and hosted on G2.com.

There was some upfront effort needed to get everyone aligned with the new standard. Teams that were used to maintaining their own base images needed a bit of time to adjust and adapt to the new approach. Review collected by and hosted on G2.com.

The biggest win for us is how minimal the images are. There’s no unnecessary clutter, and that immediately reduced the number of CVEs we were seeing in our pipeline. The daily rebuilds are a huge plus, since we no longer have to constantly monitor upstream patches ourselves. I also appreciate the built-in SBOMs, because they provide clear visibility into what’s actually running. Overall, it fits nicely into our CI/CD workflow without requiring any major changes. Review collected by and hosted on G2.com.

Debugging can be a bit more challenging because the images are distroless. You don’t have the usual tools available inside the container, so troubleshooting requires a different approach and a bit more planning than you might be used to. Review collected by and hosted on G2.com.

What stood out immediately was how quickly the CVE count dropped after we switched to Minimus images. Our scans looked much cleaner, which in turn made reviews easier and less time-consuming. Knowing the images are rebuilt from source gives me more confidence than simply applying patches on top. It also integrates smoothly into our existing pipeline without requiring major changes. Overall, it feels like a solid foundation for our workflow rather than a quick fix. Review collected by and hosted on G2.com.

There’s a bit of a learning curve when working with minimal images, especially for teams that are used to having full OS layers available. We had to adjust some of our debugging workflows to fit that model. The documentation is generally good, but it could be more detailed in a few specific areas. Review collected by and hosted on G2.com.

The compliance-ready images are very useful. Having built-in alignment with FIPS and NIST saves a lot of preparation work. SBOM generation is automatic, which is a big help during audits and reduces the need for manual tracking significantly. Review collected by and hosted on G2.com.

The initial onboarding required coordination across multiple teams. It wasn’t difficult, but it did take some planning and alignment. I also think a few of the customization steps could be documented more clearly to make the process smoother. Review collected by and hosted on G2.com.

Minimus gives us a secure default without needing a large security team. The minimal images and regular rebuilds take care of a lot of things we would otherwise have to manage manually. Instead of constantly worrying about outdated packages and unnecessary software inside our containers, we can start from base images that are already designed with security in mind. Review collected by and hosted on G2.com.

Teams that previously used a full Linux distro inside the container may need some time to adjust their build process. Review collected by and hosted on G2.com.

The main reason we started using it was to reduce the number of vulnerabilities in our container environments. We run an internal web application, and our security scans used to generate long lists that we weren’t really using. After moving to minimal images, the vulnerability reports became much shorter and easier to manage. Review collected by and hosted on G2.com.

The images are very minimal, which is great for security, but it also meant our dev team had to adjust the build process. Review collected by and hosted on G2.com.

The distroless approach makes a big difference. The images include only what’s needed to run the application, which reduces unnecessary complexity and lowers the number of vulnerabilities we see during scanning. This also helps standardize our container builds, because every team starts from the same minimal base image. Review collected by and hosted on G2.com.

The team needs to adjust their Docker files and build process, because many common packages aren’t included by default. Review collected by and hosted on G2.com.

We deal with a lot of connected devices across control panels, IP cameras, and intercoms, and keeping track of the vulnerabilities across all of them was genuinely painful before we started using Minimus. Our old process was basically running scans manually, which made it hard to stay on top of everything. Review collected by and hosted on G2.com.

The Jira integration isn’t very good, and it doesn’t work as well as I expected. Review collected by and hosted on G2.com.

We use containers heavily on our platform, and the biggest advantage for us has been standardization. Every team now uses the same minimal base image, which has reduced environment differences between development, testing, and production. Review collected by and hosted on G2.com.

Because the image is minimal, some teams initially tried to install extra tools and ended up making the image larger again. Review collected by and hosted on G2.com.

Minimus addresses several issues we typically see with container images. The hardened images reduce the attack surface, and the fact that they’re built with a minimal set of dependencies makes a noticeable difference in vulnerability management. Review collected by and hosted on G2.com.

Teams that are used to fully featured image tools may need some time to adjust to the build process and the workflows. Review collected by and hosted on G2.com.