# Air Gapped EPR Size

**URL:** <https://discuss.elastic.co/t/air-gapped-epr-size/380294>\
**Category:** Kibana\
**Tags:** docker\
**Created:** [July 21, 2025, 10:46am UTC](https://discuss.elastic.co/t/air-gapped-epr-size/380294 "2025-07-21T10:46:21Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Stuart\_M](https://avatars.discourse-cdn.com/v4/letter/s/c0e974/32.png) [@Stuart\_M](https://discuss.elastic.co/u/Stuart_M)\
**Post date:** [July 21, 2025, 10:46am UTC](https://discuss.elastic.co/t/air-gapped-epr-size/380294/1 "2025-07-21T10:46:22Z")

</div>

I'm deploying Elastic into an air gapped environment where we host the Elastic Package Registry (EPR) locally. We currently pull down the latest one on a monthly basis, but it is starting to get pretty large (25GB+). Looking inside the .tar file I can see that it has many, many versions of the integrations listed. Is it possible to only bring down a specific version? Or if not, is there a method to reduce the size? I've tried the 'lite' version but it is missing some of the integrations which we use.

---

<div class="post-metadata">

**Author:** ![gezg](https://avatars.discourse-cdn.com/v4/letter/g/a9a28c/32.png) [@gezg](https://discuss.elastic.co/u/gezg)\
**Post date:** [July 22, 2025, 11:12am UTC](https://discuss.elastic.co/t/air-gapped-epr-size/380294/2 "2025-07-22T11:12:39Z")

</div>

...same here, 210gb just to load a 22gb 9.0.0 epr docker image then a further 47gb to get the container running seems a bit excessive! I woudl hate to think how much storage we need to allocate for 9.0.3 and later as teh package size just keeps growing and growing....