oracle/docker-images

Slim Oracle Database image

Open

#1,265 建立於 2019年5月2日

在 GitHub 查看
 (1 留言) (5 反應) (1 負責人)Shell (6,139 star) (5,379 fork)batch import
databasehelp wantedquestion

描述

We are migrating from the Docker store/oracle/database-enterprise:12.2.0.1-slim image to building from this GH repo using the SingleInstance files.

One thing we've noticed immediately is that the size of the resulting images is 3x bigger (2G for the store -slim image, 6G for the GH version).

Aside from using the --squash experimental Docker feature, are there aspects of the Oracle Database image that could safely be removed? We note the products/ space seems to be where the bulk of the file size is, but we're not sure if there are possibly optional components that we could safely remove in our post-setup step.

貢獻者指南

技術棧
shelldocker
領域
devopsinfrastructure
議題類型
performance
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
4
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
3-5 days
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
blocked
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
Docker image optimizationOracle DB installation structureLinux file system basics
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
25
研究方向
Investigate the Dockerfiles in the SingleInstance directory to identify which Oracle components are installed. The `products/` directory likely contains large binaries; check if any can be removed (e.g., unused language packs, documentation). Consider multi stage builds to copy only essential files. Review the single comment on the issue for any hints.