Skip to main content
Version: v2.5

Deploying Console into Air-Gapped Environments

When deploying management console into an air-gapped environment, you need to ensure that the console has access to the required images.

Docker Images​

You can download the images and upload them into internal docker registry.

docker pull quay.io/deepfenceio/deepfence_worker:2.5.3
docker pull quay.io/deepfenceio/deepfence_server:2.5.3
docker pull quay.io/deepfenceio/deepfence_ui:2.5.3
docker pull quay.io/deepfenceio/deepfence_file_server:2.5.3
docker pull quay.io/deepfenceio/deepfence_agent:2.5.3
docker pull quay.io/deepfenceio/deepfence_cluster_agent:2.5.3
docker pull quay.io/deepfenceio/deepfence_router:2.5.3
docker pull quay.io/deepfenceio/deepfence_redis:2.5.3
docker pull quay.io/deepfenceio/deepfence_kafka_broker:2.5.3
docker pull quay.io/deepfenceio/deepfence_postgres:2.5.3
docker pull quay.io/deepfenceio/deepfence_neo4j:2.5.3
docker pull quay.io/deepfenceio/deepfence_compliance_scanner:2.5.3
docker pull quay.io/deepfenceio/deepfence_telemetry:2.5.3
export IMAGE_REPOSITORY=127.0.0.1:5000

docker tag quay.io/deepfenceio/deepfence_worker:2.5.3 ${IMAGE_REPOSITORY}/deepfence_worker:2.5.3
docker tag quay.io/deepfenceio/deepfence_server:2.5.3 ${IMAGE_REPOSITORY}/deepfence_server:2.5.3
docker tag quay.io/deepfenceio/deepfence_ui:2.5.3 ${IMAGE_REPOSITORY}/deepfence_ui:2.5.3
docker tag quay.io/deepfenceio/deepfence_file_server:2.5.3 ${IMAGE_REPOSITORY}/deepfence_file_server:2.5.3
docker tag quay.io/deepfenceio/deepfence_agent:2.5.3 ${IMAGE_REPOSITORY}/deepfence_agent:2.5.3
docker tag quay.io/deepfenceio/deepfence_cluster_agent:2.5.3 ${IMAGE_REPOSITORY}/deepfence_cluster_agent:2.5.3
docker tag quay.io/deepfenceio/deepfence_router:2.5.3 ${IMAGE_REPOSITORY}/deepfence_router:2.5.3
docker tag quay.io/deepfenceio/deepfence_redis:2.5.3 ${IMAGE_REPOSITORY}/deepfence_redis:2.5.3
docker tag quay.io/deepfenceio/deepfence_kafka_broker:2.5.3 ${IMAGE_REPOSITORY}/deepfence_kafka_broker:2.5.3
docker tag quay.io/deepfenceio/deepfence_postgres:2.5.3 ${IMAGE_REPOSITORY}/deepfence_postgres:2.5.3
docker tag quay.io/deepfenceio/deepfence_neo4j:2.5.3 ${IMAGE_REPOSITORY}/deepfence_neo4j:2.5.3
docker tag quay.io/deepfenceio/deepfence_compliance_scanner:2.5.3 ${IMAGE_REPOSITORY}/deepfence_compliance_scanner:2.5.3
docker tag quay.io/deepfenceio/deepfence_telemetry:2.5.3 ${IMAGE_REPOSITORY}/deepfence_telemetry:2.5.3
docker tag quay.io/deepfenceio/deepfence_agent:fargate-2.5.3 ${IMAGE_REPOSITORY}/deepfence_agent:2.5.3
export IMAGE_REPOSITORY=127.0.0.1:5000

docker push ${IMAGE_REPOSITORY}/deepfence_worker:2.5.3
docker push ${IMAGE_REPOSITORY}/deepfence_server:2.5.3
docker push ${IMAGE_REPOSITORY}/deepfence_ui:2.5.3
docker push ${IMAGE_REPOSITORY}/deepfence_file_server:2.5.3
docker push ${IMAGE_REPOSITORY}/deepfence_agent:2.5.3
docker push ${IMAGE_REPOSITORY}/deepfence_cluster_agent:2.5.3
docker push ${IMAGE_REPOSITORY}/deepfence_router:2.5.3
docker push ${IMAGE_REPOSITORY}/deepfence_redis:2.5.3
docker push ${IMAGE_REPOSITORY}/deepfence_kafka_broker:2.5.3
docker push ${IMAGE_REPOSITORY}/deepfence_postgres:2.5.3
docker push ${IMAGE_REPOSITORY}/deepfence_neo4j:2.5.3
docker push ${IMAGE_REPOSITORY}/deepfence_compliance_scanner:2.5.3
docker push ${IMAGE_REPOSITORY}/deepfence_telemetry:2.5.3

Now follow the documentation here to deploy the console using the internal registry.

env IMAGE_REPOSITORY=127.0.0.1:5000 docker compose up -d

ThreatIntel database​

You can download the latest ThreatIntel database and upload it in Settings page.

Scan history & Threat Intel
Scan history & Threat Intel