知识卡片

普通读书笔记卡 · 8746 · 生成模型:GPT-6

镜像边界按依赖共享程度划分

理解等级:中级

开发、生产服务和部署工具所需依赖不同。全部塞进一镜像会增加体积和暴露面,每个小任务一镜像又增维护成本;可按共享与独有依赖聚合,明确每类镜像承担哪些进程。

这张卡片看不懂?

已有反馈 · 0 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • · 查看原书依据

      Identifying What to Containerize The first and most important step in Dockerizing a project is to disambiguate exactly what we are containerizing. This can confuse some ML practitioners and can lead to conflated and shared states. For example, if we share an image between the two distinct tasks of developing an ML model and serving an ML model, we may find unnecessary development dependencies (e.g.,

    参考来源

    - 位置:《Effective Machine Learning Teams (David Tan, Ada Leung, David Colls)》第04章《依赖管理实践》(来源项目:a19c7933-4eda-4176-aebd-30fe7e1ad292;源文件:extracted/Effective Machine Learning Teams (David Tan, Ada Leung, David Colls)/_epub-src/OEBPS/ch04.html) - 结论依据:摘录中关于镜像边界按依赖共享程度划分的定义、比较或条件支撑卡片;原书表述不严谨的范围已在覆盖记录逐项限定,不把案例结果外推为普遍结论。 - 原始内容:Identifying What to Containerize The first and most important step in Dockerizing a project is to disambiguate exactly what we are containerizing. This can confuse some ML practitioners and can lead to conflated and shared states. For example, if we share an image between the two distinct tasks of developing an ML model and serving an ML model, we may find unnecessary development dependencies (e.g.,