Air-gapped (isolated from internet) environments cannot pull images directly from public registries. To deploy an APMInsight agent Docker image in such an environment:
.tar file.Agent | Docker Hub Image |
Java | site24x7/apminsight-javaagent |
.NET | site24x7/apminsight-dotnetagent |
PHP | site24x7/apminsight-phpagent |
Python | site24x7/apminsight-pythonagent |
Node.js | site24x7/apminsight-nodejsagent |
<agent-image> with the image name from the table above, and <tag> with the required version (or latest)..tar file to a machine with access to your private registry, using SCP, SFTP, USB drive, or any approved file transfer method.# On the internet-enabled machine
docker pull site24x7/apminsight-javaagent:latest
docker save -o apminsight-javaagent.tar site24x7/apminsight-javaagent:latest
# On the machine with access to the private registry
docker load -i apminsight-javaagent.tar
docker tag site24x7/apminsight-javaagent:latest myregistry.example.com/apminsight-javaagent:latest
docker login myregistry.example.com
docker push myregistry.example.com/apminsight-javaagent:latest
Onboarding steps (Kubernetes/OpenShift InitContainers, Docker Compose, etc.) are agent-specific — refer to the onboarding documentation for the agent you deployed. Replace the public image reference in that documentation with your private repository image URL.