Reduce Image Size?

[philipbjorge]

Is there room to reduce the docker image size?

The 1GB+ pull is slowing down our Github Actions compared to other containers (e.g. cp-kafka and postgres)

[matty-at-rdc]

Dreaming of the day

[theUm]

I'm totally fine with a single docker layer of 1.3gb that fetches something from staging-confluent-packages-something-something.s3.us-west-2.amazonaws.com that leads to final image to be 1.7 GB

https://hub.docker.com/layers/confluentinc/cp-schema-registry/latest-ubi8/images/sha256-b0f1473e9b724ada5338390346438229206f3568ccee94d78bdff1f37e3c8c52?context=explore

[j-tim]

The big image (2+ GB) slows us down (in pipelines and automated test suites) and introduces dependencies that are most likely not needed to run the container.

Observation on the Confluent Platform Schema Registry Docker image, it contains:

• Red Hat Enterprise OS
• Azule JDK instead of a smaller JRE

Is Confluent accepting contributions to improve the size of this image?

[spockz]

One tiny thing that I found is that after installing modules via pip the resulting cache in /root/.cache/pip doesn't get cleared. Saves only 17MiB. Interestingly enough, the command showing in dive is

I did manage to build a native-image of the schema registry with GraalVM. But there is a lot of surrounding scripting in various languages just to determine some startup flags. It would reduce the image with ±300MiB as the binary itself is ±200MiB.

[spockz]

I have created a new image based on RHEL9 and a native-image build of the schema registry. This gets the size down to 214MiB and startup time to 1s.

• Schema Registry Image
• Repo for Schema Registry Image
• Branch of 8.2.0 + native-image changes

Is anyone from Confluent interested in adding a native-image build and releasing the native-image version of the docker image?