Templates Library

What this screen is for

The Templates Library is a catalogue of predefined Dockerfile templates you can start from instead of writing a container build by hand. Pick the template matching your stack, generate, adjust.

Before you start

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

Opening it

  1. Tools › Templates Library in the sidebar.

Direct URL: /developer-tools/predefined-templates-library

The interface

📸 Screenshot Placeholder: The Templates Library. Mark: (1) the template list, (2) one template’s card, (3) the action that opens a template.

# Control What it does When you’d use it
1 Template list The predefined Dockerfile templates Browsing for your stack
2 Template card What the template is for Choosing
3 Open Loads the template into the generator Once you have chosen

Opening a template takes you to the generator at /developer-tools/predefined-templates-library/:template.

Walkthroughs

Generate a Dockerfile from a template

  1. Tools › Templates Library.
  2. Find the template matching your stack.
  3. Open it. The generator loads with that template applied.
  4. Adjust the generated Dockerfile and commit it to your repository.

Start from nothing instead

If no template fits, use the Image Builder at /developer-tools/from-scratch-docker-generator, which is reachable normally from Build › Image Builder.

Scenario

Containerising a service whose stack you have not packaged before.

  1. Tools › Templates Library — look for the template matching the stack, not the framework. Templates are organised around the runtime, because that is what determines the base image and the build steps.
  2. Open it and read what it produces before generating. A template that almost fits is worth adapting; one that fits badly costs more than starting from scratch.
  3. Generate, then adjust. The output is a starting point, not a finished Dockerfile — image size and layer caching are yours to tune.
  4. Commit it to the repository, then connect that repository in Settings › Development › Repositories if it is not already.
  5. Scan the built image with Security Scanner before it reaches an environment. A base image chosen from a template is still a base image you now own.

If no template matches, Image Builder builds one from scratch and is reachable from Build › Image Builder.

When it doesn’t work

Symptom Cause How to check Fix
Page is blank or refused Missing the Dockerfile read permission Access Explorer Ask for a role granting it
No template fits your stack The library is a fixed set Use Image Builder

Next