[{"data":1,"prerenderedAt":680},["ShallowReactive",2],{"navigation":3,"\u002Fdocs\u002Fdocker\u002Fbasic":158,"\u002Fdocs\u002Fdocker\u002Fbasic-description":669},[4],{"title":5,"path":6,"stem":7,"children":8,"page":36},"Docs","\u002Fdocs","docs",[9,37,45,65,148],{"title":10,"description":11,"icon":12,"path":13,"stem":14,"children":15,"page":36},"Redis","Redis是一个开源的高性能键值存储数据库，它提供了多种数据结构来存储数据，如字符串、哈希、列表、集合、有序集合等。Redis将数据存储在内存中，以提供快速的读写访问速度，并且能够通过异步的方式将数据持久化到磁盘上。它支持复制、Lua脚本、事务处理、不同级别的持久化选项以及多种客户端语言的接口。Redis广泛用于缓存、消息队列、短时数据存储和高性能的应用场景中。","skill-icons:redis-light","\u002Fdocs\u002Fredis","docs\u002F1.redis",[16],{"title":17,"path":18,"stem":19,"children":20,"description":34,"icon":35},"install","\u002Fdocs\u002Fredis\u002Finstall","docs\u002F1.redis\u002F1.install\u002F1.index",[21,24,29],{"title":22,"path":18,"stem":19,"description":23},"Introduction","The powerful Git-based CMS designed specifically for Nuxt developers.",{"title":25,"path":26,"stem":27,"description":28},"Installation","\u002Fdocs\u002Fredis\u002Finstall\u002Finstallation","docs\u002F1.redis\u002F1.install\u002F2.installation","Get started with Nuxt Content v3 in your Nuxt application.",{"title":30,"path":31,"stem":32,"description":33},"Configuration","\u002Fdocs\u002Fredis\u002Finstall\u002Fconfiguration","docs\u002F1.redis\u002F1.install\u002F3.configuration","Nuxt Content is configured with sensible defaults.",null,"icon-park-outline:install",false,{"title":38,"path":39,"stem":40,"children":41,"description":43,"icon":44},"SpringBoot","\u002Fdocs\u002Fspringboot","docs\u002F2.springboot\u002F1.index",[42],{"title":22,"path":39,"stem":40,"description":23},"Spring Boot 是一个基于 Spring 框架的‌开箱即用型 Java 开发框架‌，由 Pivotal 团队于 2014 年推出，旨在彻底简化 Spring 应用的初始搭建、配置和部署流程。其核心理念是 ‌\"约定优于配置\"‌，通过自动化机制减少开发者的样板代码工作，显著提升效率。","simple-icons:springboot",{"title":46,"path":47,"stem":48,"children":49,"description":63,"icon":64},"Rocky Linux","\u002Fdocs\u002Frocky","docs\u002F3.rocky\u002F1.index",[50,53,58],{"title":51,"path":47,"stem":48,"description":52},"1 Rocky Linux 概述","Rocky Linux 是一个开源、免费的企业级 Linux 操作系统。它的核心目标是与 Red Hat Enterprise Linux (RHEL) 100% 完全兼容，可以看作是原本广受欢迎的 CentOS 的“替代者”和“精神继承者.",{"title":54,"path":55,"stem":56,"description":57},"2 VMware安装Rocky Linux","\u002Fdocs\u002Frocky\u002Finstall","docs\u002F3.rocky\u002F2.install","本文主要介绍了VMware Workstation 17.x 虚拟机如何快速安装Rocky Linux 10.x 版本的Linux操作系统。",{"title":59,"path":60,"stem":61,"description":62},"3 Rocky Linux 10安装Docker","\u002Fdocs\u002Frocky\u002Fdocker","docs\u002F3.rocky\u002F3.docker","在 Rocky Linux 10 上安装 Docker 的推荐方式是使用其官方仓库。下面是完整的安装步骤。","Rocky Linux 是一个开源、免费的企业级 Linux 操作系统。它的核心目标是与 Red Hat Enterprise Linux (RHEL) 100% 完全兼容，可以看作是原本广受欢迎的 CentOS 的“替代者”和“精神继承者”","logos:rocky-linux-icon",{"title":66,"description":67,"icon":68,"path":69,"stem":70,"children":71,"page":36},"Docker","Docker是一个开源的应用容器引擎，可以让开发者打包他们的应用以及依赖包到一个轻量级、可移植的容器中，然后发布到Docker容器中运行，也可以实现虚拟化。","devicon:docker","\u002Fdocs\u002Fdocker","docs\u002F4.docker",[72,96,111,137],{"title":73,"path":74,"stem":75,"children":76,"description":34,"icon":95},"Docker 基础","\u002Fdocs\u002Fdocker\u002Fbasic","docs\u002F4.docker\u002F1.basic\u002F1.index",[77,80,85,90],{"title":78,"path":74,"stem":75,"description":79},"Docker基础概念","Docker是一个基于Go语言开发并遵从 Apache2.0 协议开源的应用容器引擎，可以让开发者打包他们的应用以及依赖包到一个轻量级、可移植的容器中，然后发布到Docker环境中运行，容器彼此隔离，但可以通过特定的通道相互传递信息。保证了在任何环境下运行的应用程序具有相同的行为，这极大地减少了环境差异导致的“在我机器上可以运行”的问题。",{"title":81,"path":82,"stem":83,"description":84},"Docker核心架构","\u002Fdocs\u002Fdocker\u002Fbasic\u002Fdocker-architecture","docs\u002F4.docker\u002F1.basic\u002F2.docker-architecture","Docker 采用 C\u002FS 架构，客户端通过 REST API 将指令下达给常驻后台的守护进程（dockerd）；守护进程则依靠 Linux 内核的 Namespace 实现环境隔离、Cgroups 实现资源配额，并利用 UnionFS 的分层存储机制构建镜像和容器，从而在单台宿主机上实现了轻量级、高性能的应用沙箱。",{"title":86,"path":87,"stem":88,"description":89},"Docker镜像加速","\u002Fdocs\u002Fdocker\u002Fbasic\u002Fdocker-mirror-acceleration","docs\u002F4.docker\u002F1.basic\u002F3.docker-mirror-acceleration","Docker安装完成后默认的官方镜像仓库是[Docker Hub‌](https:\u002F\u002Fhub.docker.com\u002F){target=blank}，这是Docker官方维护的公共镜像注册中心。但对于国内Docker用户而言，在没有魔法的情况下是无法访问Docker Hub网站的，也无法从Docker Hub仓库拉取镜像。目前国内常用的2种方法：**Docker镜像加速源** 和 **配置Docker代理**。",{"title":91,"path":92,"stem":93,"description":94},"Docker Context","\u002Fdocs\u002Fdocker\u002Fbasic\u002Fdocker-context","docs\u002F4.docker\u002F1.basic\u002F4.docker-context","Docker Context 是 Docker 19.03 版本引入的一项功能，它为 Docker 客户端（CLI）提供了一套标准化的“连接配置”机制。通过 Context，你可以轻松地在本地开发环境、远程服务器、云服务等多个 Docker 环境之间快速切换，极大地提升了多环境管理的效率。","mdi:information-box-outline",{"title":97,"description":34,"icon":35,"path":98,"stem":99,"children":100,"page":36},"Docker 安装","\u002Fdocs\u002Fdocker\u002Finstall","docs\u002F4.docker\u002F2.install",[101,106],{"title":102,"path":103,"stem":104,"description":105},"CentOS安装Docker","\u002Fdocs\u002Fdocker\u002Finstall\u002Fcentos-docker-install","docs\u002F4.docker\u002F2.install\u002F1.centos-docker-install","在 CentOS 上安装 Docker，准确的说是安装 Docker Engine, 本文主要介绍如何在CentOS上安装Docker。",{"title":107,"path":108,"stem":109,"description":110},"Rocky安装Docker","\u002Fdocs\u002Fdocker\u002Finstall\u002Frocky-docker-install","docs\u002F4.docker\u002F2.install\u002F2.rocky-docker-install","在 Rocky Linux 10 上安装 Docker 和 Centos 安装 Docker 步骤基本类似的，推荐方式是使用其官方仓库。下面是完整的安装步骤。",{"title":112,"description":34,"icon":113,"path":114,"stem":115,"children":116,"page":36},"Docker 使用","fluent:data-usage-24-regular","\u002Fdocs\u002Fdocker\u002Fusage","docs\u002F4.docker\u002F3.usage",[117,122,127,132],{"title":118,"path":119,"stem":120,"description":121},"Docker持久化","\u002Fdocs\u002Fdocker\u002Fusage\u002Fdocker-persistence","docs\u002F4.docker\u002F3.usage\u002F1.docker-persistence","在 Docker 中，容器默认是无状态的，容器删除后内部数据会直接丢失，Docker 官方提供了三类核心数据持久化方案，分别适配不同的使用场景：卷（Volumes）、绑定挂载（Bind Mounts） 和 tmpfs 挂载。",{"title":123,"path":124,"stem":125,"description":126},"Docker容器自启动","\u002Fdocs\u002Fdocker\u002Fusage\u002Fcontainer-restart","docs\u002F4.docker\u002F3.usage\u002F2.container-restart","Docker容器自启动策略是指Docker服务运行期间，特定容器在退出、崩溃或宿主机重启后，容器是否自动重新运行。",{"title":128,"path":129,"stem":130,"description":131},"Docker Dockerfile","\u002Fdocs\u002Fdocker\u002Fusage\u002Fdocker-dockerfile","docs\u002F4.docker\u002F3.usage\u002F3.docker-dockerfile","本文旨在探讨Dockerfile的功能定位与指令体系，并在此基础上，给出基于Dockerfile实现自定义镜像构建的具体方法。",{"title":133,"path":134,"stem":135,"description":136},"连接远程Docker服务","\u002Fdocs\u002Fdocker\u002Fusage\u002Fconnect-remote-docker","docs\u002F4.docker\u002F3.usage\u002F4.connect-remote-docker","在日常开发或测试中，我们经常需要在本地开发环境中直接操作远程 Docker 服务——执行镜像构建、容器启停等命令，效果与直接在远程服务器上操作完全一致。这能极大提升调试与部署效率，同时避免频繁登录远程服务器的繁琐。",{"title":138,"description":34,"icon":139,"path":140,"stem":141,"children":142,"page":36},"Docker 参考手册","material-symbols-light:docs-outline","\u002Fdocs\u002Fdocker\u002Fresources","docs\u002F4.docker\u002F5.resources",[143],{"title":144,"path":145,"stem":146,"description":147},"Docker 命令大全","\u002Fdocs\u002Fdocker\u002Fresources\u002Fdocker-command","docs\u002F4.docker\u002F5.resources\u002F1.docker-command","下面介绍Docker常见的基础命令。",{"title":149,"path":150,"stem":151,"children":152,"description":156,"icon":157},"Linux","\u002Fdocs\u002Flinux","docs\u002F5.Linux\u002F1.index",[153],{"title":154,"path":150,"stem":151,"description":155},"1.dnf和yum区别","一句话概括：dnf 是 yum 的下一代升级版，你可以把 dnf 看作\"优化重构后的yum\"","Linux是免费开源、多用户多任务、高稳定性与安全性、支持多平台硬件的Unix操作系统。文档整理了Linux相关的命令和常见问题处理方法。","logos:linux-tux",{"id":159,"title":78,"body":160,"createDate":655,"description":79,"extension":656,"links":657,"meta":661,"navigation":662,"path":74,"readingTime":663,"seo":664,"sitemap":665,"stem":75,"updateDate":666,"wordCount":667,"__hash__":668},"docs\u002Fdocs\u002F4.docker\u002F1.basic\u002F1.index.md",{"type":161,"value":162,"toc":642},"minimark",[163,168,172,175,179,182,217,221,224,229,255,260,280,284,422,426,470,474,477,501,504,507,510,513,517,520,546,550,553],[164,165,167],"h2",{"id":166},"_1-什么是容器化技术","1. 什么是容器化技术",[169,170,171],"p",{},"容器化技术‌是一种操作系统层面的轻量级软件虚拟化方法，它将应用程序及其所有依赖项（代码、运行时、库、配置等）打包到标准化的独立环境中，让应用能在不同计算环境中一致运行。",[169,173,174],{},"它利用Linux内核的命名空间实现进程、网络、文件系统的资源隔离，通过控制组（Cgroups）限制CPU、内存等资源占用，多个容器共享同一主机内核，无需像虚拟机那样启动完整操作系统，因此具备启动速度快、资源占用极低、环境完全一致的核心优势，是云原生、微服务架构的核心支撑技术。",[164,176,178],{"id":177},"_2-容器化技术的特性","2. 容器化技术的特性",[169,180,181],{},"容器化技术是一种基于操作系统级虚拟化的软件打包与运行机制，其核心特性为‌轻量共享内核、强隔离环境、高度可移植、秒级启停及弹性伸缩‌。‌‌",[183,184,185,193,199,205,211],"ul",{},[186,187,188,192],"li",{},[189,190,191],"strong",{},"轻量高效："," 共享宿主机操作系统内核，无需独立系统实例，资源占用少、启动速度快（秒级），显著提升服务器密度与利用率 。",[186,194,195,198],{},[189,196,197],{},"进程级隔离‌："," 利用命名空间（Namespaces）和控制组（cgroups）实现文件系统、网络、进程及资源的相互隔离，故障互不干扰 。",[186,200,201,204],{},[189,202,203],{},"‌环境一致性与可移植性‌："," 将应用代码、运行时、依赖库及配置打包为不可变镜像，确保开发、测试、生产环境行为完全一致，支持跨平台（x86\u002FARM 等）及多云无缝迁移 。",[186,206,207,210],{},[189,208,209],{},"‌快速部署与弹性伸缩："," 支持镜像版本化管理，可实现秒级扩缩容，完美适配微服务架构与 CI\u002FCD 流水线。",[186,212,213,216],{},[189,214,215],{},"资源可控‌："," 可精确限制和分配 CPU、内存、I\u002FO 等资源配额，保障关键业务性能稳定性 。‌‌",[164,218,220],{"id":219},"_3-容器化的核心理念","3. 容器化的核心理念",[169,222,223],{},"容器化的核心理念是‌通过操作系统级虚拟化实现“一次打包，处处运行”‌，将应用及其依赖封装为‌不可变、隔离且标准化的轻量级单元‌，确保环境一致性与资源高效利用：",[169,225,226],{},[189,227,228],{},"1. 核心要素",[183,230,231,237,243,249],{},[186,232,233,236],{},[189,234,235],{},"不可变基础设施‌："," 镜像构建后严禁修改，任何变更需重新构建并替换实例，杜绝配置漂移与环境差异 。",[186,238,239,242],{},[189,240,241],{},"‌进程级隔离与资源受限‌："," 利用 Linux Namespace 实现文件系统、网络、进程等视图隔离，通过 Cgroups 精确限制 CPU、内存等资源配额 。",[186,244,245,248],{},[189,246,247],{},"‌环境标准化与可移植性‌："," 将代码、运行时、库及配置打包为统一镜像，消除“在我机器能跑”问题，支持跨平台无缝部署 。",[186,250,251,254],{},[189,252,253],{},"轻量共享内核‌："," 共享宿主机操作系统内核，无需独立 Guest OS，实现秒级启动与高密度资源利用率（相比虚拟机资源开销降低 70% 以上）。‌‌",[169,256,257],{},[189,258,259],{},"2. 技术支撑机制",[183,261,262,268,274],{},[186,263,264,267],{},[189,265,266],{},"‌Namespace‌："," 提供 PID、NET、MNT 等独立视图，实现逻辑隔离。",[186,269,270,273],{},[189,271,272],{},"‌Cgroups‌："," 管控资源使用上限，防止单容器耗尽宿主机资源。",[186,275,276,279],{},[189,277,278],{},"‌联合文件系统 (UnionFS)‌："," 支持镜像分层存储与快速增量构建，提升分发效率。",[164,281,283],{"id":282},"_4-docker的核心概念","4. Docker的核心概念",[183,285,286,330,372],{},[186,287,288,291],{},[189,289,290],{},"容器（Container）：",[183,292,293,299],{},[186,294,295,298],{},[189,296,297],{},"概念："," 容器是镜像的运行实例，是一个轻量级、可移植的执行环境，包含应用代码、运行时环境和依赖库。",[186,300,301,304],{},[189,302,303],{},"特点：",[183,305,306,312,318,324],{},[186,307,308,311],{},[189,309,310],{},"隔离性："," 每个容器都有自己的文件系统、网络和进程空间。",[186,313,314,317],{},[189,315,316],{},"临时性："," 容器可以被创建、启动、停止、删除。",[186,319,320,323],{},[189,321,322],{},"可写层："," 容器在镜像基础上添加了一个可写层。",[186,325,326,329],{},[189,327,328],{},"进程级："," 容器内通常运行一个主进程。",[186,331,332,335],{},[189,333,334],{},"镜像（Image）：",[183,336,337,342],{},[186,338,339,341],{},[189,340,297],{}," 镜像是一个只读的模板，包含了运行应用所需的所有内容：代码、运行时、库文件、环境变量和配置文件，定义了容器的运行环境（如操作系统、软件配置等）。通过分层存储（Layer）优化空间和构建速度。",[186,343,344,346],{},[189,345,303],{},[183,347,348,354,360,366],{},[186,349,350,353],{},[189,351,352],{},"分层存储："," 镜像由多个层组成，每一层代表一次修改。",[186,355,356,359],{},[189,357,358],{},"只读性："," 镜像本身是只读的，不能直接修改。",[186,361,362,365],{},[189,363,364],{},"可复用："," 同一个镜像可以创建多个容器。",[186,367,368,371],{},[189,369,370],{},"版本管理："," 通过标签(tag)进行版本管理。",[186,373,374,377],{},[189,375,376],{},"仓库（Registry）：",[183,378,379,384,409],{},[186,380,381,383],{},[189,382,297],{}," 仓库是存储和分发镜像的地方，可以包含一个镜像的多个版本.",[186,385,386,389],{},[189,387,388],{},"分类：",[183,390,391,397,403],{},[186,392,393,396],{},[189,394,395],{},"公共仓库："," 如 Docker Hub，任何人都可以使用。",[186,398,399,402],{},[189,400,401],{},"私有仓库："," 企业内部搭建，用于存储私有镜像。",[186,404,405,408],{},[189,406,407],{},"官方仓库："," 由软件官方维护的镜像仓库。",[186,410,411,414],{},[189,412,413],{},"Registry vs Repository：",[183,415,416,419],{},[186,417,418],{},"Registry：仓库注册服务器，如 Docker Hub",[186,420,421],{},"Repository：具体的镜像仓库，如 nginx、mysql",[164,423,425],{"id":424},"_5-docker的技术优势","5. Docker的技术优势",[183,427,428,434,440,446,452,458,464],{},[186,429,430,433],{},[189,431,432],{},"轻量级与高效性："," 与传统的虚拟机相比，Docker 容器更加轻量级，因为它们共享操作系统内核，而不是为每个实例创建一个完整的操作系统。这不仅减少了资源开销，还提升了启动速度，使得容器可以在几秒钟内启动并运行。",[186,435,436,439],{},[189,437,438],{},"一致性与可移植性："," Docker 提供了从开发到生产的一致环境。通过将应用程序及其依赖项打包到容器中，Docker 保证了在任何环境下运行的应用程序具有相同的行为，这极大地减少了环境差异导致的“在我机器上可以运行”的问题。",[186,441,442,445],{},[189,443,444],{},"快速部署与扩展："," Docker 容器化的应用程序可以在几秒钟内启动，从而显著加快了部署过程。由于容器的轻量特性，用户可以在同一台物理服务器上运行更多的容器实例，快速扩展应用程序的规模以应对需求变化。",[186,447,448,451],{},[189,449,450],{},"微服务架构支持："," Docker 非常适合微服务架构，因为它允许将应用程序的不同组件封装在独立的容器中。这种隔离不仅提高了应用程序的模块化程度，还简化了开发、测试和部署过程。",[186,453,454,457],{},[189,455,456],{},"资源利用与隔离："," Docker 容器在同一主机上共享操作系统内核，同时通过 cgroups 和命名空间等技术实现了资源的严格隔离。这样，Docker 容器可以高效利用系统资源，并确保不同容器之间的安全隔离。",[186,459,460,463],{},[189,461,462],{},"广泛的生态系统与工具支持："," Docker 拥有丰富的生态系统，包括 Docker Hub、Docker Compose、Docker Swarm 等工具，支持从开发到生产的各个环节。用户可以方便地从 Docker Hub 获取公共镜像，利用 Docker Compose 管理多容器应用，或使用 Docker Swarm 进行容器编排。",[186,465,466,469],{},[189,467,468],{},"DevOps 和 CI\u002FCD 友好："," Docker 与持续集成和持续交付（CI\u002FCD）流程高度契合。通过将应用程序打包成 Docker 镜像，开发者可以在任何阶段快速部署、测试和发布应用，从而加快开发周期并提高交付效率。",[164,471,473],{"id":472},"_6-docker的技术局限","6. Docker的技术局限",[169,475,476],{},"Docker并不是全能的，设计之初也不是KVM之类虚拟化手段的替代品，简单总结几点：",[478,479,480,483,486,489,492,495,498],"ol",{},[186,481,482],{},"Docker是基于64位Linux的，无法在32位的linux\u002FWindows\u002Funix环境下使用。",[186,484,485],{},"libcontainer利用了cgroup等linux kernel功能，因此容器的guest系统只能是linux base的。",[186,487,488],{},"隔离性相比KVM之类的虚拟化方案有所欠缺，所有容器公用一部分的运行库。",[186,490,491],{},"网络管理相对简单，主要是基于namespace隔离。",[186,493,494],{},"cgroup的cpu和cpuset提供的cpu功能相比KVM的等虚拟化方案相比难以度量。",[186,496,497],{},"Docker对disk的管理比较有限。",[186,499,500],{},"容器随着用户进程的停止而销毁，容器中的log等用户数据不便收集。",[169,502,503],{},"Docker在本质上是一个附加系统。使用分层架构构建一个应用是可行的。每个组件被添加到之前已经创建的组件之上；另一方面，分层架构带来另一方面的效率提升，当重建存在变化的Docker镜像时，不需要重建整个Docker镜像，只需要重建变化的部分。",[169,505,506],{},"可能更为重要的是，Docker旨在用于弹性计算。每个Docker实例的运营生命周期有限，实例数量根据需求增减。在一个管理适度的系统中，这些实例生而平等，不再需要时便各自消亡了。",[169,508,509],{},"针对Docker环境存在的不足，意味着在开始部署Docker前需要考虑如下几个问题。首先，Docker实例是无状态的。这意味着它们不应该承载任何交易数据，所有数据应该保存在数据库服务器中。",[169,511,512],{},"其次，开发Docker实例并不像创建一台虚拟机、添加应用然后克隆那样简单。为成功创建并使用Docker基础设施，管理员需要对系统管理的各个方面有一个全面的理解，包括Linux管理、编排及配置工具比如Puppet、Chef以及Salt。这些工具生来就基于命令行以及脚本。",[164,514,516],{"id":515},"_7-docker的应用场景","7. Docker的应用场景",[169,518,519],{},"广泛用于微服务架构部署、CI\u002FCD持续交付、跨平台开发、边缘计算、AI模型训练推理等场景，是当前云原生技术栈的核心基础。",[183,521,522,528,534,540],{},[186,523,524,527],{},[189,525,526],{},"微服务架构："," 每个服务独立容器化，便于管理和扩展。",[186,529,530,533],{},[189,531,532],{},"CI\u002FCD流水线："," 与 Jenkins\u002FGitLab CI 集成，实现自动化构建和测试。",[186,535,536,539],{},[189,537,538],{},"开发环境标准化："," 新成员一键启动全套依赖服务（如数据库、消息队列）。",[186,541,542,545],{},[189,543,544],{},"云原生基础："," Kubernetes 等编排工具基于 Docker 管理容器集群。",[164,547,549],{"id":548},"_8-docker与虚拟机","8. Docker与虚拟机",[169,551,552],{},"Docker与虚拟机是两种不同层级的虚拟化技术，核心差异集中在架构原理、资源表现和适用场景上，具体区别如下：",[554,555,556,572],"table",{},[557,558,559],"thead",{},[560,561,562,566,569],"tr",{},[563,564,565],"th",{},"特性",[563,567,568],{},"虚拟机",[563,570,571],{},"Docker容器",[573,574,575,587,598,609,620,631],"tbody",{},[560,576,577,581,584],{},[578,579,580],"td",{},"启动速度",[578,582,583],{},"分钟级",[578,585,586],{},"秒级",[560,588,589,592,595],{},[578,590,591],{},"内核",[578,593,594],{},"每个 VM 有独立内核",[578,596,597],{},"共享宿主机内核",[560,599,600,603,606],{},[578,601,602],{},"资源占用",[578,604,605],{},"高（GB 级别）",[578,607,608],{},"低（MB 级别）",[560,610,611,614,617],{},[578,612,613],{},"隔离级别",[578,615,616],{},"强（硬件级隔离）",[578,618,619],{},"较强(操作系统级的进程隔离)",[560,621,622,625,628],{},[578,623,624],{},"交付一致性",[578,626,627],{},"镜像大，环境一致",[578,629,630],{},"镜像小，环境一致",[560,632,633,636,639],{},[578,634,635],{},"性能损耗",[578,637,638],{},"虚拟机有虚拟化硬件损耗",[578,640,641],{},"Docker 接近原生性能",{"title":643,"searchDepth":644,"depth":644,"links":645},"",3,[646,648,649,650,651,652,653,654],{"id":166,"depth":647,"text":167},2,{"id":177,"depth":647,"text":178},{"id":219,"depth":647,"text":220},{"id":282,"depth":647,"text":283},{"id":424,"depth":647,"text":425},{"id":472,"depth":647,"text":473},{"id":515,"depth":647,"text":516},{"id":548,"depth":647,"text":549},"2026-07-04 09:29:00","md",[658],{"label":659,"icon":68,"to":660},"官网地址","https:\u002F\u002Fwww.docker.com\u002F",{},{"title":78},15.7,{"title":78,"description":79},{"loc":74},"2026-07-21 11:11:34",2829,"BJHl5CJu4Dva3Nz5p7Lpy7-aukaDF2UoAXJpwalSKQo",{"data":670,"body":671},{},{"type":672,"children":673},"root",[674],{"type":675,"tag":169,"props":676,"children":677},"element",{},[678],{"type":679,"value":79},"text",1787625811571]