Introducing Docker init: Automated Generation of Dockerfiles and Compose Files

Many developers find writing Dockerfile and docker‑compose.yml files painful; Docker has released a new CLI utility called docker init that leverages generative AI to help generate these resources with minimal noise.

docker init is a command‑line tool that initializes Docker resources in a project, creating a .dockerignore , a Dockerfile , and a compose file based on the project's language (Go, Python, Node.js, Rust, ASP.NET, PHP, Java) and works alongside Docker Desktop.

To use it, navigate to the project directory, create the necessary source files (e.g., a simple Flask app), and run docker init . Example setup files:

touch app.py requirements.txt

# app.py
from flask import Flask
app = Flask(__name__)

@app.route('/')
def hello_docker():
    return '
hello world
'

if __name__ == '__main__':
    app.run(debug=True, host='0.0.0.0')

# requirements.txt
Flask

Running docker init scans the project, prompts you to select a template that matches the application type, and then generates the appropriate Docker configuration files.

docker init

The tool then asks you to confirm the platform (e.g., Python) and suggests values such as the Python version, port, and entrypoint command.

Below is an example of the automatically generated Dockerfile :

# syntax=docker/dockerfile:1

# Comments are provided throughout this file to help you get started.
# If you need more help, visit the Dockerfile reference guide at
# https://docs.docker.com/engine/reference/builder/

ARG PYTHON_VERSION=3.11.7
FROM python:${PYTHON_VERSION}-slim as base

ENV PYTHONDONTWRITEBYTECODE=1
ENV PYTHONUNBUFFERED=1

WORKDIR /app

ARG UID=10001
RUN adduser \
    --disabled-password \
    --gecos "" \
    --home "/nonexistent" \
    --shell "/sbin/nologin" \
    --no-create-home \
    --uid "${UID}" \
    appuser

RUN --mount=type=cache,target=/root/.cache/pip \
    --mount=type=bind,source=requirements.txt,target=requirements.txt \
    python -m pip install -r requirements.txt

USER appuser
COPY . .
EXPOSE 5000
CMD gunicorn 'app:app' --bind=0.0.0.0:5000

The generated compose.yaml (shown as an image in the original article) sets up the service to run the Flask application and, because the example has no database, comments out any database container configuration.

Using docker init makes containerizing an application effortless, especially for newcomers, by eliminating manual creation of Dockerfiles and related configuration, saving time, reducing mistakes, and automatically applying industry‑standard best practices.

In summary, docker init writes better Docker configurations than most developers, follows security and performance best practices, and helps avoid the hundreds of potential vulnerabilities that static analysis tools might otherwise report.

Disclaimer: Like any AI‑based tool, docker init is not perfect. Do not blindly trust the generated configuration; review it before using it in production.