Building AI Solutions with Docker Compose and Kubernetes Expertise

Compose 2.x: A Dev Tool That Grew Up#

Compose is still your best friend for local work. No argument there. But it’s also a serious CI/CD asset now, and a genuinely good staging orchestrator, if you know how to drive it.

Enough preamble.

Environment Variable Precedence: Know Who Wins the Fight#

By default, Compose favors your shell environment over whatever sits in your .env file.

So this:

1
export DATABASE_URL=postgres://prod.db

…will override this in .env:

1
DATABASE_URL=postgres://dev.db

Good. That’s exactly the behavior you want in CI/CD, where secrets have no business touching source control.

📖 Environment Variables — Compose Docs

Controlling Image Pulls: Don’t Get Burned by Stale Containers#

There are two clean ways to pull fresh images.

1. Force it every time:

   1
   docker compose up --pull always
   

2. Lock it in the Compose file:

   1
   services:
   2
     app:
   3
       image: my-image:latest
   4
       pull_policy: always
   

pull_policy supports: always, if_not_present, and never.

Use it. Skip it and you’ll burn an afternoon debugging a bug that doesn’t exist, because CI quietly served a stale image from cache while you screamed at your pipeline.

SSH & Secrets: Handling Sensitive Stuff Like an Adult#

BuildKit is the default now. That buys you real control over build-time secrets and SSH access.

1
services:
2
  app:
3
    build:
4
      context: .
5
      ssh:
6
        - default=/home/user/.ssh/id_rsa

Live Reloads with docker compose watch: Real Dev Speed#

You want a tight feedback loop. That’s what the watch command is for.

1
services:
2
  app:
3
    image: node:18
4
    volumes:
5
      - .:/app
6
    working_dir: /app
7
    command: npm start
8
    environment:
9
      NODE_ENV: development
10
    ports:
11
      - "3000:3000"
12
    labels:
13
      com.docker.compose.watch: "true"

1
docker compose up
2
docker compose watch

Override Files: Keep Dev and Prod from Colliding#

Still cramming every config into one compose.yaml? Stop. Split it:

• compose.override.yaml for local tweaks
• docker compose -f base.yaml -f prod.yaml to layer configs
• include: blocks, if you’re on Compose v2+ and feeling fancy

It’s cleaner, it’s safer, and it’s a lot easier to debug when something breaks at 2am.

📖 Extending Compose Files

YAML Anchors: DRY or Die#

Compose files turn into spaghetti fast. Anchors fix that:

1
x-default-env: &default-env
2
  NODE_ENV: production
3

4
services:
5
  web:
6
    image: webapp
7
    environment: *default-env
8

9
  api:
10
    image: apiserver
11
    environment:
12
      <<: *default-env
13
      DEBUG: true

Less repetition, fewer bugs, and a file you can actually read six months from now.

📖 Compose File Fragments

Resource Limits: Be a Good Container Citizen#

Even on a dev cluster, don’t let one container eat the whole node.

1
services:
2
  ai-worker:
3
    image: my-ai-image
4
    deploy:
5
      resources:
6
        limits:
7
          cpus: "1.0"
8
          memory: "1G"
9
        reservations:
10
          cpus: "0.5"
11
          memory: "512M"

Now, a caveat. deploy is ignored by docker compose in local mode. But the second you hand this off to Swarm or translate it to Kubernetes, you’ll be glad it was already there.

Compose to Kubernetes: The Good, The Bad, and The “Use Kompose”#

Want to turn a Compose stack into Kubernetes YAMLs? Kompose does it, and the output isn’t terrible.

1
kompose convert

You’ll still have homework:

• Set up Ingress and controllers by hand
• Configure PVCs and storage
• Handle secrets the Kubernetes way

For MVPs and small internal tools, though, it works fine.

Just don’t ship the raw output to production. Clean it up first.

Final Take#

Docker Compose stopped being a one-trick Redis-launcher a while ago. Driven well, it’s a serious tool, and it earns its keep most in AI workflows, the kind that sprawl across a dozen services.

It lets you:

• Develop locally at full speed
• Keep secrets out of your images
• Cut downtime during builds
• Hand off to Kubernetes when the time comes

If you’re shipping AI services and you’re not using Compose properly, you’re just making the job harder than it is.

📖 Read the Full Compose Docs