possible mismatch between stacks/google_gae_22/run-packages.txt and Google Cloud documentation

[StephenWithPH]

I'm looking at the contents of:

buildpacks/stacks/google_gae_22/run-packages.txt

Lines 1 to 129 in 168979f

	ca-certificates
	curl
	ffmpeg
	file
	fontconfig
	fonts-freefont-ttf
	fonts-ipafont-gothic
	fonts-kacst
	fonts-liberation
	fonts-thai-tlwg
	fonts-wqy-zenhei
	git
	ghostscript
	gnupg
	imagemagick
	iputils-ping
	libasound2
	libatk-bridge2.0-0
	libatk1.0-0
	libatspi2.0-0
	libblas3
	libbz2-1.0
	libc-bin
	libc6
	libcairo2
	libcups2
	libcurl4
	libcurl4-openssl-dev
	libdb5.3
	libdbus-1-3
	libdrm2
	libenchant-2-2
	libexpat1
	libffi8
	libfftw3-double3
	libflac8
	libfontconfig1
	libfontenc1
	libfreetype6
	libgbm1
	libgcc-s1
	libgcrypt20
	libgd3
	libgdbm6
	libgdk-pixbuf-2.0-0
	libgdk-pixbuf2.0-common
	libglib2.0-0
	libgmp10
	libgmpxx4ldbl
	libgoogle-perftools4
	libgraphite2-3
	libgs9
	libgs9-common
	libgssapi-krb5-2
	libhashkit2
	libicu70
	libjbig0
	libjbig2dec0
	libjpeg-turbo8
	libjpeg8
	libk5crypto3
	libkeyutils1
	libkrb5-3
	libkrb5-3
	libkrb5support0
	liblapack3
	libldap-2.5-0
	libldap-common
	liblzma5
	libmemcached11
	libmemcachedutil2
	libmpc3
	libmpdec3
	libmysqlclient21
	libnghttp2-14
	libnspr4
	libnss3
	libonig5
	libpango-1.0-0
	libpangocairo-1.0-0
	libpng16-16
	libpq5
	libprotoc23
	libpsl5
	libreadline8
	librsvg2-2
	librsvg2-common
	librtmp1
	libsasl2-2
	libsasl2-modules
	libsasl2-modules-db
	libsnappy1v5
	libsodium23
	libsqlite3-0
	libssl3
	libstdc++6
	libtidy5deb1
	libtiff5
	libtiffxx5
	libuuid1
	libvpx7
	libwebp7
	libx11-6
	libxcb1
	libxcomposite1
	libxdamage1
	libxext6
	libxfixes3
	libxkbcommon0
	libxml2
	libxrandr2
	libxrender1
	libxslt1.1
	libyaml-0-2
	libzip4
	locales
	locales-all
	lsb-release
	mime-support
	netbase
	nginx-core
	openssl
	python3-chardet
	tzdata
	unzip
	uuid-runtime
	wget
	xdg-utils
	zlib1g

.. whose associated readme suggests determines the packages in us-docker.pkg.dev/serverless-runtimes/google-22-full/run:

buildpacks/stacks/google_gae_22/README.md

Lines 6 to 10 in 168979f

	## Run Image
	[us-docker.pkg.dev/serverless-runtimes/google-22-full/run](https://us-docker.pkg.dev/serverless-runtimes/google-22-full/run)
	Available packages listed in [run-packages.txt](./run-packages.txt)

Should those packages align with the list of packages on https://cloud.google.com/docs/buildpacks/stacks#google-22-full ?

Specifically, the Google Cloud docs show liblcms2-2 2.12~rc1-2build2 included in the google-22-full stack, but that package does not appear in this repo's stacks/google_gae_22/run-packages.txt .

[StephenWithPH]

For clarity, I'm looking into this due to the apparent absence of liblcms2.so.2 in a Google Cloud buildpacks-built JVM application. It's a vanilla build, deployed to Cloud Run.

It strikes me as odd that we're encountering this error, since the Ubuntu jre (which is what I think corresponds to these log lines):

 [builder] === Java - Runtime ([email protected]) ===
[builder] Using requested runtime feature version: 21
[builder] 2024/12/10 22:07:27 [DEBUG] GET https://dl.google.com/runtimes/ubuntu2204/canonicaljdk/version.json
[builder] ***** CACHE MISS: "canonicaljdk"
[builder] Installing  v21.0.5+11-Ubuntu-1ubuntu122.04.
[builder] 2024/12/10 22:07:27 [DEBUG] GET https://dl.google.com/runtimes/ubuntu2204/canonicaljdk/canonicaljdk-21.0.5_11-Ubuntu-1ubuntu122.04.tar.gz

... has a transitive dependency on that:

https://packages.ubuntu.com/jammy/openjdk-21-jre -> https://packages.ubuntu.com/jammy/openjdk-21-jre-headless -> https://packages.ubuntu.com/jammy/liblcms2-2 .

I can't find enough insight on the machinery that gcr.io/buildpacks/builder:latest uses to assemble all of the pieces, so I don't know if that dependency is getting dropped somewhere.

There is this issue in the unrelated distroless repo which suggests that something might be missing here: GoogleContainerTools/distroless#329