Docker and Kubernetes Container Practice Handbook
A Chinese-language ZIP handbook for images, containers, workloads, services, configuration and deployment troubleshooting.
What this container handbook covers
This Chinese-language ZIP archive follows a container learning path from images and containers to Kubernetes workloads, services, configuration and troubleshooting. It is useful for connecting an application's runtime boundary with Pod, Deployment, Service, ConfigMap and Secret responsibilities.
The English page is a searchable summary and file guide. The source material remains in Chinese; image tags, APIs, defaults and commands should be checked against the versions used in each exercise.
A layered practice path
Start with one fixed image and a disposable container, then add ports, volumes and logs. Move the same application into a small workload, expose it through a service, and document configuration, health checks, resource limits and rollback points.
File and scope note
The indexed ZIP is 326.47 MB. Its size makes selective extraction useful; retain the archive and copy only the chapters needed for a lab. Content review date: 2026-08-23.
Save to your cloud drive
Save the complete collection first so files remain together and are easier to access across devices.
Quark Cloud Drive
RecommendedSave Docker and Kubernetes Container Practice Handbook to this cloud drive
Baidu Netdisk
Save Docker and Kubernetes Container Practice Handbook to this cloud drive
Docker and Kubernetes practice guide
Work from one local container to a small Kubernetes workload while recording image versions, configuration sources, health checks and recovery steps.
Before you start
- Know basic Linux commands, network ports and YAML syntax.
- Have a ZIP extractor and an isolated container or local cluster environment.
- Prepare a lab record for image tags, resource limits, configuration sources and rollback points.
Quick start
- 01
Select the lab slice
Extract the directory or chapter needed for one exercise, inspect version markers and keep the original archive separate.
- 02
Run one container
Fix an image tag, test port mapping, volumes and logs, and record the boundary between the container and host.
- 03
Map the workload objects
Describe how Pod, Deployment, Service, ConfigMap and Secret each support the same application scenario.
- 04
Record release and rollback
Keep image, configuration, probe, resource and rollback details beside each change and test a failure path in the lab.
Usage tips
- Manage image tags, configuration and secrets separately; keep credentials outside images and public examples.
- Validate probes, resource limits and logs before discussing scaling; a small lab does not establish production capacity.
- Attach component versions to commands and API objects because defaults and APIs evolve.
Troubleshooting and uninstall
The extracted archive uses too much space. What is a useful workflow?
Inspect the directory and chapter list, copy only the required material into the lab, and preserve enough temporary space for extraction.
A Pod starts but the service is unreachable. Which signals should I check?
Check container logs, readiness, port mapping, Service selectors, namespace and network policy in that order.
Frequently asked questions
How should Docker and Kubernetes be studied together?
Start with images and containers, then map the same application to Pods, Deployments, Services, configuration and cluster troubleshooting.
Why record component versions?
Image layers, APIs, defaults and command behavior vary by version, so version notes make an experiment reproducible.
Is this handbook a production deployment design?
It is a learning and documentation reference; production work still needs supply-chain, credentials, networking, persistence, monitoring and rollback review.