Open philipbjorge opened 1 year ago
Dreaming of the day
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
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:
Is Confluent accepting contributions to improve the size of this image?
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
andpostgres
)