When building a new Kogito Service with the CLI/Operator, one might face the following error:
[INFO] [io.quarkus.resteasy] Resteasy running without servlet container. [INFO] [io.quarkus.resteasy] - Add quarkus-undertow to run Resteasy within a servlet container [INFO] [io.quarkus.deployment.pkg.steps.JarResultBuildStep] Building thin jar: /tmp/src/target/kogito-travel-agency-1.0-SNAPSHOT-runner.jar [INFO] [io.quarkus.deployment.QuarkusAugmentor] Quarkus augmentation completed in 24600ms [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 01:25 min [INFO] Finished at: 2019-10-28T14:11:43Z [INFO] ------------------------------------------------------------------------ 'target/kogito-travel-agency-1.0-SNAPSHOT-runner.jar' -> '/home/kogito/bin/kogito-travel-agency-1.0-SNAPSHOT-runner.jar' ---> Copy image metadata file... '/tmp/src/target/image_metadata.json' -> '/tmp/.s2i/image_metadata.json' '/tmp/src/target/image_metadata.json' -> '/home/kogito/bin/image_metadata.json' error: Execution of post execute step failed error: build error: label validation failed for "172.30.1.1:5000/openshift/kogito-quarkus-ubi8-s2i@sha256:2d18c994f32da15cd6560be81719da7e294372bc93796ad2a9067a6bae9a5f40" image: label size '14509' exceeds the maximum limit '10240'
This is likely to happen on custom image labels that have more than 3 proto files with 5 attributes.
Until we change the way we deploy the proto files, a "known issue" should be listed in the docs with a workaround to increase this limit, if possible:
https://docs.openshift.com/container-platform/3.11/admin_guide/limits.html#image-limits
- relates to
-
KOGITO-497 Codegen is adding the kogito-application.proto file in the image_metadata.json
-
- Closed
-
