Why Containerization Lets You ‘Mop Up’ Work: A Real‑World Journey

Article originally reposted from 佳华云原生实践, thanks for the source.

After hearing the term “containerization” repeatedly at open‑source conferences, the author wondered what it actually meant. A GPT‑generated explanation describes containerization as a lightweight virtualization technology that packages applications with all dependencies, offering environment consistency, dependency management, fast startup, elasticity, isolation, security, continuous delivery, and multi‑cloud support.

The author shares a personal story of their team’s containerization effort, describing the tedious steps of compiling, killing services, backing up code, and copying files to a development server—moments he humorously calls “mop‑up” time.

Seeking help from a senior colleague, the author studied GitLab CI, Docker, and Kubernetes, eventually setting up an automated pipeline using GitLab‑Runner, Docker, and Kubernetes. The moment the pipeline succeeded felt like a breakthrough.

After further testing, the author proudly shared the results with the team chat, sparking lively discussion among developers, product managers, and senior engineers. The senior asked a few clarifying questions, leading the team to create a tool that integrates into front‑ and back‑end frameworks, automatically generating Dockerfiles and Kubernetes manifests.

Finally, the author notes that after a morning of “mopping” (slacking off) and hard work, it’s time for a break and lunch.