# Help configuring EPR to contain ONLY custom integrations **URL:** \ **Category:** Elastic Search\ **Tags:** docker\ **Created:** [March 5, 2025, 10:30pm UTC](https://discuss.elastic.co/t/help-configuring-epr-to-contain-only-custom-integrations/375487 "2025-03-05T22:30:11Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![David\_Johnson](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/david_johnson/32/141833_2.png) [@David\_Johnson](https://discuss.elastic.co/u/David_Johnson)\ **Post date:** [March 5, 2025, 10:30pm UTC](https://discuss.elastic.co/t/help-configuring-epr-to-contain-only-custom-integrations/375487/1 "2025-03-05T22:30:11Z")
Hi folks, I'm trying to set up Elastic in an air gapped environment. I've read all the documentation I could find on the topic, but the thin I'm having an issue with is running the Elastic Package Registry as a Docker image (in Kubernetes) which will serve ONLY our custom-built integrations. I've cloned the [EPR repo](https://github.com/elastic/package-registry) and am able to successfully build an image and attach a volume that contains my custom integrations (as built by Elastic-Package), but when I run the container, it is serving no content. Logs show that it finds the integrations that I have included, but when I attempt to look for them (via the /search endpoint), it returns a null set. What do I need to do to get the EPR to serve my custom integrations? Thanks for any help ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [April 2, 2025, 10:30pm UTC](https://discuss.elastic.co/t/help-configuring-epr-to-contain-only-custom-integrations/375487/2 "2025-04-02T22:30:13Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.