Auto-sync: 2026-04-18 17:09
This commit is contained in:
47
wiki/concepts/Docker-容器化.md
Normal file
47
wiki/concepts/Docker-容器化.md
Normal file
@@ -0,0 +1,47 @@
|
||||
---
|
||||
id: Docker-容器化
|
||||
title: "Docker 容器化"
|
||||
type: concept
|
||||
tags:
|
||||
- Docker
|
||||
- Containerization
|
||||
- Cloud-Migration
|
||||
- DevOps
|
||||
last_updated: 2026-04-18
|
||||
---
|
||||
|
||||
## Aliases
|
||||
- Containerization
|
||||
- Containerize
|
||||
|
||||
## Summary
|
||||
- **定义**:使用 Docker 容器技术将应用程序及其依赖打包为标准化单元的过程
|
||||
- **目的**:实现应用的可移植性、一致性和隔离性
|
||||
- **云迁移价值**:将遗留应用容器化是云就绪的关键步骤
|
||||
|
||||
## Key Details
|
||||
- **核心优势**:
|
||||
- 跨环境一致性(开发、测试、生产)
|
||||
- 资源隔离和高效利用
|
||||
- 快速部署和弹性伸缩
|
||||
- 简化迁移流程(lift-and-shift)
|
||||
- **适用场景**:
|
||||
- 微服务架构
|
||||
- 云迁移(lift-and-shift)
|
||||
- 持续集成/持续部署(CI/CD)
|
||||
- 开发环境标准化
|
||||
- **限制**:
|
||||
- 容器内数据持久化需要额外机制(Volume)
|
||||
- 有状态应用的容器化复杂度较高
|
||||
- 不适合数据库等有状态服务直接运行
|
||||
|
||||
## Octane Hub 案例
|
||||
- Octane Hub 使用 Docker 容器运行各种 Web 应用(QuickSee、Release Manager、Patch Manager)
|
||||
- 容器化使其能够从本地数据中心无缝迁移到 AWS
|
||||
- 数据库未直接容器化,使用 EBS 而非 EFS 存储
|
||||
|
||||
## Connections
|
||||
- [[Dockerfile]] ← defines ← [[Docker-容器化]]
|
||||
- [[Docker-Image]] ← builds ← [[Docker-容器化]]
|
||||
- [[Octane-Hub]] ← uses ← [[Docker-容器化]]
|
||||
- [[Cloud-Migration]] ← enabled_by ← [[Docker-容器化]]
|
||||
Reference in New Issue
Block a user