Docs

Image Builder

What this screen is for

Image Builder generates Dockerfiles: you describe the image you want in a form, and it produces a Dockerfile you can adjust and commit. It exists so that containerising a service does not start with copying someone else’s Dockerfile and hoping.

Two ways in — a blank form, or a pre-filled template from the Templates Library.

Before you start

To do this You need
Open Image Builder the local-env Dockerfile read permission

Opening it

Build › Image Builder in the sidebar.

Direct URL: /developer-tools/from-scratch-docker-generator

📸 Screenshot Placeholder: The Image Builder form, empty. Mark: (1) the base image field, (2) the build steps area, (3) the exposed ports field, (4) the generate action.

Overview

The Image Builder is a developer-focused tool within the Fenwave Internal Developer Platform (IDP) that simplifies the creation of production-ready Dockerfiles. It offers two starting points for the same powerful generator: start with a blank form to build from scratch, or choose a pre-configured template that you can fully customize.

Key Capabilities:

  • Flexible Starting Points - Begin with a blank form or choose from pre-filled templates
  • Template Library - Quick-start templates for Node.js, Python, Java, Go, and more
  • Live Preview - See your Dockerfile update in real-time as you configure options
  • Drag-and-Drop Reordering - Rearrange some Dockerfile instructions visually
  • Security Scanning - Integrated Trivy vulnerability scanning for generated Dockerfiles
  • Instant Download - Download your validated Dockerfile with a single click

Scenario

A service with no Dockerfile, going into an environment next week.

  1. Check the Templates Library first. Starting from a template that fits the runtime saves more than the form does.
  2. If nothing fits, Build › Image Builder and start from blank.
  3. Fill the form — see Dockerfile Generator. Get the base image right before anything else; every later decision follows from it.
  4. Generate, then read what came out. It is a starting point, not a finished artefact — layer ordering and image size are yours to tune.
  5. Commit it to the repository.
  6. Run Security Scanning before it reaches an environment. A base image you chose from a form is still a base image you now own, vulnerabilities included.

When it doesn’t work

Symptom Cause How to check Fix
Image Builder is not in the Build submenu Missing the Dockerfile read permission Access Explorer Ask for a role granting it
The generated Dockerfile does not build The form describes intent, not a validated build Build it locally Adjust and rebuild; the generator does not compile it for you
No template matches your stack The library is a fixed set Templates Library Start from blank

Next