关于Ignite Web Console最新Docker镜像及Dockerfile的技术咨询

1. Latest Docker Image for Ignite Web Console #

The official apacheignite/web-console-standalone image on Docker Hub is often outdated, which explains the compatibility mismatch with your newer web agent. Unfortunately, the official Docker Hub repository hasn’t been updated consistently for recent Ignite releases.

Here’s what you can do:

• Check for version-specific tags (e.g., apacheignite/web-console-standalone:2.15.0) on Docker Hub to see if there’s a tagged image that matches your web agent’s version.
• If no matching tag exists, build the latest image yourself using the official source code (details in the next section).

2. Official Dockerfiles to Skip From-Scratch Builds #

Absolutely—Apache Ignite provides ready-to-use Dockerfiles for the Web Console in its source code repo. You won’t need to build everything from zero:

• Clone the Ignite repository and navigate to the modules/web-console/docker directory (this holds Dockerfiles for the standalone console and related components).
• Build your custom image with this command in the Dockerfile’s directory:

  docker build -t custom-ignite-web-console .
  

This will pull all required dependencies and create a console image aligned with the latest source code, which should be fully compatible with your web agent.

3. Dockerfile to Combine Web Agent and Console in One Image #

There’s no official pre-built image that merges both, but you can easily create a custom one by extending the official console image and adding the web agent setup. Here’s a working example:

# Use the latest official console image as base (replace with a specific version if needed)
FROM apacheignite/web-console-standalone:latest

# Install required tools
RUN apt-get update && apt-get install -y unzip curl && rm -rf /var/lib/apt/lists/*

# Download and extract web agent matching your console version
ARG AGENT_VERSION=2.15.0
RUN curl -O https://archive.apache.org/dist/ignite/${AGENT_VERSION}/apache-ignite-web-agent-${AGENT_VERSION}.zip && \
    unzip apache-ignite-web-agent-${AGENT_VERSION}.zip -d /opt/ignite-web-agent && \
    rm apache-ignite-web-agent-${AGENT_VERSION}.zip

# Configure agent to connect to local console
ENV AGENT_CONSOLE_URL=http://localhost:3000
ENV AGENT_NODE_NAME=integrated-agent

# Create startup script to run both services
RUN echo '#!/bin/bash' > /usr/local/bin/start-services.sh && \
    echo "echo Starting Ignite Web Console..." >> /usr/local/bin/start-services.sh && \
    echo "/opt/ignite-web-console/start.sh &" >> /usr/local/bin/start-services.sh && \
    echo "sleep 10" >> /usr/local/bin/start-services.sh && \
    echo "echo Starting Ignite Web Agent..." >> /usr/local/bin/start-services.sh && \
    echo "/opt/ignite-web-agent/bin/ignite-web-agent.sh" >> /usr/local/bin/start-services.sh && \
    chmod +x /usr/local/bin/start-services.sh

# Set startup script as container command
CMD ["start-services.sh"]

Key Notes for This Combined Image: #

• Ensure AGENT_VERSION matches your console’s version to avoid compatibility issues.
• The sleep 10 gives the console time to initialize before the agent connects—adjust this duration if needed for your environment.
• For production, consider using Docker Compose to run separate containers for the console and agent instead; it’s more flexible for scaling and maintenance.

内容的提问来源于stack exchange，提问作者DonTequila