ilum/coreEnterprise Apache Spark orchestration platform for Kubernetes, enabling serverless data processing at scale.
 docker run -d \ --name ilum-core \ -p 9000:9000 \ -e MONGO_URI=mongodb://mongo:27017/ilum \ -e SPRING_KAFKA_BOOTSTRAP_SERVERS=kafka:9092 \ ilum/core:<version>
Note: For production deployments, use the official Ilum Helm Chart.
<version>: Ilum 6.6.1 + Spark orchestration engine + Java 21| Variable | Description |
|---|---|
| MONGO_URI | MongoDB connection string for metadata storage |
| SPRING_KAFKA_BOOTSTRAP_SERVERS | Kafka brokers for inter-service communication |
| ILUM_STORAGE_MINIO_URL | MinIO endpoint for Spark artifacts and logs |
| ILUM_STORAGE_MINIO_ACCESS_KEY | MinIO access key |
| ILUM_STORAGE_MINIO_SECRET_KEY | MinIO secret key |
| Variable | Default Value | Description |
|---|---|---|
| SERVER_PORT | 9000 | Ilum Core API port |
| ILUM_LIVY_PORT | 9888 | Apache Livy-compatible gateway port |
| ILUM_COMMUNICATION_TYPE | kafka | Communication mode: kafka or grpc |
NOTE:
Using grpc as communication type disables High Availability support. For production deployments with HA requirements, use kafka (default).
Ilum Core is stateless. All persistent data is stored in external infrastructure components (MongoDB, Kafka, MinIO).
TIP: For disaster recovery, ensure regular backups of MongoDB (metadata) and MinIO (Spark artifacts, event logs).
| Port | Service |
|---|---|
9000 | Ilum Core REST API + Apache Livy 0.8.0-compatible endpoints |
9888 | gRPC communication (ilum-core ↔ Spark jobs) |
The image runs as user ilum (UID 1001). Ensure that mounted volumes have appropriate permissions.
CAUTION: Never pass sensitive credentials directly in environment variables!
Recommended methods:
Before production deployment, scan the image:
bash# Trivy trivy image ilum/core:<version>
Run commands from the root of the ilum-backend repository:
bash# Build the service ./gradlew clean build # Build multi-platform Docker image ./gradlew dockerMultiplatformPush
bashdive ilum/core:<version>
bash# Syft syft ilum/core:<version> -o spdx-json > sbom.json
ilum/java:21.0.9_10-jre)The Ilum Core API is designed with an API-first approach.
Interactive API Documentation:
http://<ilum-core>:9000/docs/api/ilum-api-definition moduleAPI Version Compatibility:
| API Version | Ilum Version |
|---|---|
| 1.0.0 | <= 6.6.1 |
Long-running Spark applications that accept consecutive workload requests without re-initialization overhead. Ideal for:
Traditional batch Spark jobs submitted via API. Supports:
| Mode | Use Case | HA Support |
|---|---|---|
| Kafka | Production deployments requiring scalability and HA | ✅ Yes |
| gRPC (default) | Development/testing environments, simplified setup | ❌ No |
Ilum Core requires the following components to operate:
All dependencies are automatically deployed when using the ilum-aio Helm chart.

探索更多轩辕镜像的使用方法,找到最适合您系统的配置方式
通过 Docker 登录认证访问私有仓库
在 Linux 系统配置镜像服务
在 Docker Desktop 配置镜像
Docker Compose 项目配置
Kubernetes 集群配置 Containerd
K3s 轻量级 Kubernetes 镜像加速
在宝塔面板一键配置镜像
Synology 群晖 NAS 配置
飞牛 fnOS 系统配置镜像
极空间 NAS 系统配置服务
爱快 iKuai 路由系统配置
绿联 NAS 系统配置镜像
QNAP 威联通 NAS 配置
Podman 容器引擎配置
HPC 科学计算容器配置
ghcr、Quay、nvcr 等镜像仓库
无需登录使用专属域名
需要其他帮助?请查看我们的 常见问题Docker 镜像访问常见问题解答 或 提交工单
免费版仅支持 Docker Hub 访问,不承诺可用性和速度;专业版支持更多镜像源,保证可用性和稳定速度,提供优先客服响应。
专业版支持 docker.io、gcr.io、ghcr.io、registry.k8s.io、nvcr.io、quay.io、mcr.microsoft.com、docker.elastic.co 等;免费版仅支持 docker.io。
当返回 402 Payment Required 错误时,表示流量已耗尽,需要充值流量包以恢复服务。
通常由 Docker 版本过低导致,需要升级到 20.x 或更高版本以支持 V2 协议。
先检查 Docker 版本,版本过低则升级;版本正常则验证镜像信息是否正确。
使用 docker tag 命令为镜像打上新标签,去掉域名前缀,使镜像名称更简洁。
来自真实用户的反馈,见证轩辕镜像的优质服务