"Web Development to Deployment and Operations (2/8) — Why Docker Is the Starting Point for Environment Control"

Docker matters not mainly because it makes deployment feel modern, but because it lets an application carry its execution assumptions with it.

Key Takeaways

  • Docker fixes the execution environment into an image and runs that image as a container.
  • For beginners, Docker is most valuable not as automation hype but as a way to reduce local-versus-production drift.
  • Images, containers, networks, and volumes need to be understood separately if Docker is going to make architectural sense.
  • Docker does not solve every operational problem, but it does remove many avoidable environment excuses.

Why Docker appeared in the first place

The previous article showed that local and production systems often differ in operating system, runtime version, installed packages, system libraries, file paths, and startup commands. Even small mismatches can change behavior.

Docker appeared to reduce that gap. Instead of moving only source code, Docker packages the execution conditions the application expects. That package becomes an image, and the image can be run in a similar way across different machines.

For that reason, Docker is better understood first as a reproducibility tool. Deployment convenience is important, but environment control is the more foundational idea.

Why images and containers must be separated conceptually

Many beginners treat images and containers as almost the same thing. They are related, but their roles are different.

An image is a static blueprint. It contains the file system, dependencies, base runtime, and startup configuration required by the application. A container is a live running instance created from that image.

This distinction matters because it helps locate operational failures correctly.

  • Image problems: wrong runtime version, missing package, broken build step
  • Container problems: wrong environment variables, port conflicts, runtime state issues

If everything is called "a Docker issue," diagnosis becomes vague. Once images and containers are separated, the failure surface becomes easier to reason about.

Why beginners still benefit from Docker

Small projects can absolutely be deployed without Docker. A developer can install Node directly on a server and run the app. That is why Docker may seem unnecessary at first.

Even then, Docker gives clear benefits. Recreating the same environment on a new machine becomes easier. Working with another person becomes less dependent on undocumented version assumptions. Local testing can get closer to production conditions before any real deployment happens.

At the learning stage, Docker also acts like a teacher. Hidden dependencies that were silently satisfied on one machine become visible when the image has to describe them explicitly.

Why networking is central to Docker understanding

Beginners often imagine Docker as a way to launch one application process. Real services are usually more fragmented than that. A frontend, backend, database, cache, and reverse proxy may all be separate pieces that still need to talk to each other.

Docker networking provides the layer that defines those connections. Containers on the same network can reach each other by service name. Publicly exposed ports can be separated from private internal communication.

That makes Docker valuable as an architectural teaching tool. The world no longer looks like one localhost process. It starts to look like a system where some services are externally reachable and some should remain internal only.

Docker networking is not just about connectivity. It is about learning service boundaries.

Why volumes matter for operational thinking

Containers are designed to be replaceable. They can be recreated, restarted, and discarded. That flexibility is useful, but it also means that data stored only inside a container may disappear with the container lifecycle.

Volumes solve that by separating persistent data from the container itself. The container manages the application runtime, while the volume or external storage manages data that must survive redeploys and restarts.

That separation reduces operational risk because application replacement and data preservation are no longer treated as the same problem. The same principle will return later when this series discusses managed data platforms such as Supabase.

What Docker does not solve

It is easy to overestimate Docker and treat it like a complete answer to operations. It is not. Docker controls environment consistency, but it does not automatically fix service quality, security design, or application logic.

Problems Docker does not solve by itself include:

  • broken application logic
  • weak authentication or authorization design
  • slow queries and poor data processing
  • missing retry or fallback behavior for external APIs
  • missing logs, alerts, and monitoring

Docker provides a stronger floor, not a finished system.

What comes after environment control

Once Docker makes the runtime boundary clearer, the next question becomes more specific: what gets connected inside that controlled environment, and under what rules?

That leads naturally to API usage, tool layers such as MCP, and the limits of vibe-coding. After environment control comes dependency control.

References

  • Docker Docs, Docker overview — https://docs.docker.com/get-started/docker-overview/
  • Docker Docs, What is an image? — https://docs.docker.com/get-started/docker-concepts/the-basics/what-is-an-image/
  • Docker Docs, What is a container? — https://docs.docker.com/get-started/docker-concepts/the-basics/what-is-a-container/
  • Docker Docs, Networking in Docker — https://docs.docker.com/engine/network/
  • Docker Docs, Volumes — https://docs.docker.com/engine/storage/volumes/

This is Part 2 of the Web Development to Deployment and Operations series.

Series overview: Series index

๋Œ“๊ธ€

๋Œ“๊ธ€ ์“ฐ๊ธฐ

์ด ๋ธ”๋กœ๊ทธ์˜ ์ธ๊ธฐ ๊ฒŒ์‹œ๋ฌผ

"ML Foundations (9/9) — PyTorch vs TensorFlow, and the Road to Local LLMs"

์ด๋ฏธ์ง€
← 8/9 Deep Learning Architec… ๐Ÿ“š Series Index (series end) The final part. So far we've focused on models. Now we focus on the tools that actually run them . We'll lay out the philosophical difference between PyTorch and TensorFlow, and trace how Hugging Face transformers , llama.cpp , MLX , and Ollama built the bridge to running large language models on your own machine. By the end you should have the full mental model of "download a pretrained LLM and serve it locally." 0. Learning Objectives Explain the eager-vs-graph difference between PyTorch and TensorFlow. Explain, in graph terms, how autograd automates the backward pass. Use Hugging Face transformers ' AutoModel , AutoTokenizer , and pipeline abstractions. Describe llama.cpp's GGUF quantization, INT4 inference, and CPU-first flow. Describe Apple MLX's use of unified memory and how it differs from PyTorch. Run a local LLM with Ollama and call it through an OpenAI-compatible API. ...
Read more »

Agent Memory Engine (2/10) — Building an AI Agent Memory System with SQLite Alone

← 1/10 SQLite Memory Engine f… ๐Ÿ“š Series Index 3/10 memcore Completed → A memory engine that runs without daemons, without dependencies, anywhere ํ•ต์‹ฌ ์š”์•ฝ This post covers how to design an AI agent memory engine (memcore) on a single-file SQLite backend. - Structure: 25 modules, ~6,464 lines, 22 DB tables - Principles: no daemon, single-file portability, no required external dependencies, host-agnostic - Core techniques: 4-layer hybrid search (topic · vector · FTS5 · LIKE), U-tag dialectic-based confidence evolution, ingestion-layer bias rejection rules What This Post Covers One approach to building AI agent memory without a server or cloud vector DB. Specifically: (1) the limitations of text-file-based memory, (2) vector DB alternatives compared and selection criteria, (3) how to layer search tiers, (4) how to evolve confidence scores over time, and (5) how to block biased memory accumulation at the ingestion stage. Design Principles: Why Single-File SQLite Text-file-based ...
Read more »

"ML Foundations (8/9) — Deep Learning Architectures: CNN, RNN, Attention"

์ด๋ฏธ์ง€
← 7/9 Deep Learning Training ๐Ÿ“š Series Index 9/9 PyTorch vs TensorFlow → What did we keep adding on top of an MLP? Vision went CNN, sequences went RNN/LSTM, and eventually both converged on Attention and the Transformer. Each architecture is easier to remember if you read it as what it gave up to gain something else . This part is the one-line summary of the decisive inflection points: LeNet → AlexNet → ResNet → LSTM → Attention → Transformer. 0. Learning Objectives Explain why CNN's convolution, pooling, and weight sharing match images so well. Trace what got unblocked from LeNet → AlexNet → VGG → ResNet as depth grew. State BPTT for RNNs and the vanishing/exploding gradient problem. Write the LSTM gate equations (forget, input, output) with intuition. Write the attention formula in query/key/value form and the scaled dot-product variant. State the precise reasons Transformers replaced RNNs (parallelism + long-range dependencies). 1. ํ•ต์‹ฌ ์š”์•ฝ CNN : weight sharin...
Read more »

"RAG Core Study (14/26) — Evaluation Sets with RAGAS & DeepEval"

์ด๋ฏธ์ง€
Series overview: Series index ๐Ÿ“š Series Index Without an evaluation set, every RAG improvement is a story, not evidence. RAG systems fail in more than one place: retrieval, context selection, answer generation, and grounding. That means "looks better" is not a metric. Part 14 explains how to build a golden dataset , how RAGAS and DeepEval fit into the workflow, and why teams must separate retrieval quality from answer quality if they want tuning decisions to hold up. 0. Prerequisites Part 13 reranking — system quality now depends on multi-stage ranking. Part 1 grounding — a correct-looking answer is not enough. Part 12 Hybrid — multiple retrieval settings need comparison on fixed data. 1. Learning Objectives Build a small but useful golden dataset for RAG. Distinguish retrieval metrics from answer metrics . Use RAGAS and DeepEval in the right roles. Avoid the common traps in judge-model-based evaluation. 2. ํ•ต์‹ฌ ์š”์•ฝ An evaluation set for RAG is ...
Read more »

"ML Foundations (7/9) — Deep Learning Training: Optimizers, Regularization, Initialization"

← 6/9 Neural Networks ๐Ÿ“š Series Index 8/9 Deep Learning Architec… → Building an MLP, as we did in Part 6, is not the same as getting it to train well . The right optimizer, regularization, initialization, and learning rate — when these line up, deep networks converge. When they don't, the network refuses to learn at all. This part is the catalog of those crafts, with formulas, paper citations, and code in one place. 0. Learning Objectives Compare and write the update rules for SGD, Momentum, Nesterov, and Adam. Explain how Dropout, BatchNorm, and LayerNorm work and where they belong in a model. Derive the variance formulas for Xavier and He initialization and match them to activations. Implement step, cosine, and warmup learning-rate schedules in PyTorch. Explain why gradient clipping is effectively required for RNNs and Transformers. Diagnose the most common training failures (NaN, plateau, overfitting) and apply first-line fixes. 1. ํ•ต์‹ฌ ์š”์•ฝ SGD : \(w \leftarro...
Read more »

AI Agents I Built (5/7) — Building an Automated Blogger API Publishing System

← 4/7 My Life Organizer Agent ๐Ÿ“š Series Index 6/7 Dual → Designing a Markdown-Based Auto-Publish Pipeline with Blogger API v3 + OAuth 2.0 Key Summary Blogger API v3 + OAuth 2.0 enables a pipeline that converts Markdown files into publishable HTML posts blogger_publish.py handles the full flow — frontmatter parsing → body cleanup → HTML conversion → CSS injection → API post — in a single script For bulk publishing, quota management (delay, retry, TOC suppression) is the critical design concern Platform Selection Criteria API access is mandatory for AI agent-driven content publishing. A comparison of platforms: Platform API Cost AdSense Decision WordPress.com REST API Paid plan required Paid only Cost overhead Ghost REST API Self-hosted or paid Manual setup Ops overhead Blogger v3 API Free Native integration Adopted Blogger is free, exposes a REST API, and integrates natively with AdSense. For personal blog automation, this combination i...
Read more »

"ML Foundations (6/9) — Neural Networks: From Perceptron to MLP"

์ด๋ฏธ์ง€
← 5/9 Regularization & Model… ๐Ÿ“š Series Index 7/9 Deep Learning Training → A neural network is logistic regression from Part 4 stacked into layers. Each layer passes through a new nonlinear activation, expanding the family of functions the network can represent. In this part we put how a neural network learns onto one page. Perceptrons, XOR, MLPs, backpropagation, activation functions, and the universal approximation theorem all meet here. 0. Learning Objectives Write the perceptron's learning rule and explain why it cannot solve XOR. Express an MLP's forward pass as one line of matrix products. Derive backpropagation by hand on a two-layer MLP. Compare the definitions, derivatives, and trade-offs of sigmoid, tanh, ReLU, and GELU. State the universal approximation theorem (Cybenko 1989 / Hornik 1991) precisely. Train an MLP end-to-end in PyTorch. 1. ํ•ต์‹ฌ ์š”์•ฝ Perceptron (1958): \(\hat{y} = \mathrm{step}(w^\top x + b)\). Converges only on linearly separabl...
Read more »