Docs

Using Predefined Templates

What this screen is for

The template set the generator can start from, and how to find the one matching your stack.

Before you start

To do this You need
Browse templates the local-env Dockerfile read permission

Opening it

Tools › Templates Library.

The Templates Library offers production-ready Dockerfile templates for popular frameworks and languages. Selecting a template pre-populates the Dockerfile Generator form with optimized values that you can use as-is or customize.

📸 Screenshot Placeholder: The templates library. Mark: (1) the search and filter controls, (2) a template card, (3) the action that opens it in the generator.

Available Templates

Template Language Category Difficulty Use Case
Node.js Application JavaScript Web Application Beginner Express, NestJS, and npm-based projects
Python Flask/Django Python Web Application Beginner Python web apps with pip requirements
Java Spring Boot Java Enterprise Intermediate Maven or Gradle-based Java applications
Go Application Go Microservice Intermediate Lightweight Go microservices
Database Service SQL/NoSQL Database Beginner PostgreSQL, MySQL, MongoDB containers
Ruby on Rails Ruby Web Application Intermediate Rails apps with Bundler
PHP Laravel PHP Web Application Beginner Laravel with Composer
.NET Core C# Enterprise Intermediate ASP.NET Core web APIs

Filtering and Searching

  • Search: Type in the search box to filter by template name, description, or tags
  • Language dropdown: Filter by JavaScript, Python, Java, Go, etc.
  • Category dropdown: Filter by Web Application, Enterprise, Microservice, Database
  • Difficulty dropdown: Beginner (simple), Intermediate (complex), Advanced (production-optimized)

Using a Template

  1. Browse or search for your desired template
  2. Click “Use Template” on the template row
  3. The Dockerfile Generator opens with the template pre-loaded
  4. Modify, add, or remove fields as needed
  5. Click “Validate Dockerfile” to generate and scan your final Dockerfile

Scenario

Picking a template for a stack you have not containerised before.

  1. Filter or search by the runtime, not the framework. Templates are organised around what determines the base image and the build steps.
  2. Open the closest match and read what it produces before generating.
  3. If two are close, take the simpler one. Removing a step you do not need is easier than discovering later why an inherited one exists.
  4. Generate and adapt — see Dockerfile Generator.

When it doesn’t work

Symptom Cause How to check Fix
No template fits The set is fixed — Start from blank in Image Builder
A template produces more than you need It targets a general case The generated file Delete the steps you do not need

Next