ComponentStoreMaxSizeBytes doesn't work for components with docker image artifacts

[tomikpik]

Describe the bug
The componentStoreMaxSizeBytes config property of Nucleus does not work for components with docker image artifacts. This requires additional handling of the images downloaded on the device with constrained disk space.

To Reproduce

• set componentStoreMaxSizeBytes configuration value
• create a component with docker image artifact with size exceeding the previously set value

Expected behavior

• docker artifacts are considered in the component size in the component store

Environment

• OS: L4T 35.5.0
• JDK version: Java 17
• Nucleus version: 2.12.4

Thank you for taking a look at this

[MikeDombo]

Hello,

Yes this is known that docker images do not count for the max size. Docker images are downloaded using Docker itself which does not provide the size to Greengrass. Docker images are also not stored in the /Greengrass/v2/packages/artifacts directory.

If you want the Docker image count toward the size, the only solution now is to store the image in S3 and have the S3 link as an artifact.