AirGapped environment don't have available all packages from epr.elastic.co

[gbschenkel]

Hi, I have few airgapped clusters running on my employer.

I tried to use docker.elastic.co/package-registry/distribution:9.x.x and docker.elastic.co/package-registry/distribution:production and appears some packages or not been added to the container images, one of them is system_otel, which right now is necessary for my PoC, since we are moving to use OpenTelemetry entirelly, and use OTel Collector as Agent and EDOT Collector as Gateway.

I tried to proxy epr.elastic.co on Nexus but I am getting a few issues, which can be related to Nexus, or not.
For more information about this I have posted on Discourse/Discuss.

The system_otel can be found in here, and it state is in beta, but the documentation say about the epr been production ready.

production: docker.elastic.co/package-registry/distribution:production - Packages available in the production registry (https://epr.elastic.co/). This image is updated every time a new version of a package gets published.

[gbschenkel]

I discovered that Nexus cannot handle the dynamic proxy API when using a raw proxy, so I cannot use Nexus. The only way is to use a self-hosted package registry or directly at epr.elastic.co. Since the container image is missing some packages (~35), in my case system_otel, which I need to use, it will be necessary to allow Kibana to access epr.elastic.co directly, making the whole advantage of hosting the self-hosted package registry in an internet-isolated environment useless.

[jsoriano]

Hey, distributions don't include content packages yet, except for some exceptions.

system_otel is a content package.

In the meantime you could build your own distribution of packages. We are developing a tool to help on this task. See https://github.com/elastic/package-registry/tree/main/cmd/distribution and #1554.