We are currently encountering issues with our JFrog Installation. Our JFrog is running in Kubernetes, and initially, we had it running with regular PVCs and no problems. However, when we attempted to migrate it to MSSQL as an external database, we encountered problems with images having layers larger than 2 GB. The error received was:

error pushing image: failed to push to destination repo.dummy.com/docker/...: PATCH https://repo.dummy.com/v2/...: : org.jfrog.storage.binstore.exceptions.BinaryDbException: Could not insert Stream due to:Attempting to grow LOB beyond maximum allowed size of 2147483647 bytes.

We suspected that this might be a limitation of MSSQL, so we decided to migrate JFrog to PostgresQL as an external database. However, we encountered similar issues with large layers in images, resulting in these errors:

Docker Push Error:

error pushing image: failed to push to destination repo.dummy.com/docker/...: PATCH https://repo.dummy.com/v2/...: : org.jfrog.storage.binstore.exceptions.BinaryDbException: Could not insert Stream due to:Object is too large to send over the protocol.

JFrog Logs:

2024-06-11T13:15:35.386Z [jfrt ] [ERROR] [1d605e8db503fbbf] [c.e.m.GlobalExceptionMapper:52] [http-nio-8081-exec-8] - org.jfrog.storage.binstore.exceptions.BinaryDbException: Could not insert Stream due to:Object is too large to send over the protocol.

The expected behavior is that we should be able to upload images with larger layer sizes, exceeding 2 GB, while also utilizing an external database.