clouddevopshub/dockerfile-advance-demo

Purpose

A minimal Docker optimization demonstration. It builds the same Python application with two Dockerfiles to compare image size and likely dependency/layer practices.

Entry Point

• app.py is the application runtime entry point.

• Dockerfile.bloated and Dockerfile.optimized define alternative container build paths for that application.

• requirements.txt supplies Python dependencies to both image variants.

Application Runtime

The repository packages a Python application:

• Source: app.py

• Dependencies: requirements.txt

• Container execution is controlled by the CMD/ENTRYPOINT definitions expected in Dockerfile.bloated and Dockerfile.optimized.

Bloated Build Path

Dockerfile.bloated is the baseline image design intended to demonstrate inefficient image construction. Its architecture is the reference point for size comparison and may include unnecessary build context, package caches, broad base layers, or non-minimized dependency installation.

Optimized Build Path

Dockerfile.optimized is the alternative production-oriented build design. It packages the same app.py and requirements.txt while aiming to reduce final image size through Docker-layer and dependency/build-artifact minimization.

Build and Comparison Flow

1. Docker receives the repository directory as build context.

2. Build app:bloated from Dockerfile.bloated.

3. Build app:optimized from Dockerfile.optimized.

4. Compare resulting local image sizes using Docker image metadata.

The key boundary is build-time Docker image construction versus runtime execution of app.py; no external services, persistent infrastructure, or web-facing interface are indicated.

Material Infrastructure

• Docker daemon/build system is required.

• Python runtime is supplied by the selected Docker base images.

• Image tags app:bloated and app:optimized are local Docker artifacts.