Unnecessarily Bloated v15 Docker Images since v15.98.1

[wpyoga]

Description of the issue

Official production Docker images are unnecessarily larger since v15.98.1, due to an additional package added (chromium-headless-shell) for a feature in v16 (chromium pdf generator).

Context information (for bug reports)

Check the official Docker image sizes for v15 here: https://hub.docker.com/r/frappe/erpnext/tags?name=v15&page=2

Observe that the image sizes are as follows:

• v15.98.1
  • linux/amd64 713.99 MB
  • linux/arm64 708.9 MB
• v15.98
  • linux/amd64 533.88 MB
  • linux/arm64 525.99 MB

This is a significant increase of 180 MB. This increase can be tracked down to this commit 8b3def7 in PR #1815 . There is an extra package installed chromium-headless-shell which contributes to this increase in size.

Expected result

Since the feature is not available in v15, the package should not be installed for v15 builds.

My suggestion would be to install the package using a conditional for v16 builds only (call apt-get install a second time, but only for v16).

[DanielRadlAMR]

I’d suggest building two separate images for v15 and v16.

Currently, each container includes two Python and Node versions, which is unnecessary since only one version is used at runtime.

[wpyoga]

I'm not seeing two Python and two Node versions in the same image though. On ERPNext v15.101.3, I'm seeing these versions:

• python 3.11.6
• nodejs v20.19.2

This is using the official ERPNext Docker image.

[DanielRadlAMR]

Yeah, you're right — what I said earlier isn’t accurate. Only the bench image includes both versions, not all images.

Excluding chromium-headless-shell should be opt-out so that the current workflow for the latest version (v16) remains unchanged.

Since we’re already using build args for the Python and Node versions, I’d suggest introducing another one for this as well (e.g. INSTALL_CHROMIUM, defaulting to true).