Merge pull request #4 from G-Core/feature/mcp-server-kv-stores

Feature/mcp server kv stores ready

Author: godronus

.github/build-push-docker/action.yaml

@@ -60,6 +60,7 @@ runs:
         context: .
         file: ./Dockerfile
         push: true
+        platforms: linux/amd64,linux/arm64
         tags: ${{ steps.meta.outputs.tags }}
         labels: ${{ steps.meta.outputs.labels }}
         build-args: |

…ub/workflows/build-docker-base-image.yml …b/workflows/build-docker-base-image.yaml.github/workflows/build-docker-base-image.yml renamed to .github/workflows/build-docker-base-image.yaml .github/workflows/build-docker-base-image.yml renamed to .github/workflows/build-docker-base-image.yaml

@@ -48,6 +48,7 @@ jobs:
           context: .
           file: ./Dockerfile-base
           push: true
+          platforms: linux/amd64,linux/arm64
           tags: ${{ steps.meta.outputs.tags }}
           labels: ${{ steps.meta.outputs.labels }}
           cache-from: type=gha

.github/workflows/create-release.yml .github/workflows/create-release.yaml.github/workflows/create-release.yml renamed to .github/workflows/create-release.yaml

@@ -12,10 +12,9 @@ Edit your `.vscode/mcp.json` in your workspace with the following FASTEDGE_API_U
       "command": "bash",
       "args": [
         "-c",
-        "docker run --user $(id -u):$(id -g) --rm -i -v \"$WORKSPACE_ROOT:/workspace\" -e \"WORKSPACE_ROOT=/workspace\" -e \"FASTEDGE_API_KEY=$FASTEDGE_API_KEY\" -e \"FASTEDGE_API_URL=$FASTEDGE_API_URL\" ghcr.io/g-core/fastedge-mcp-server:latest"
+        "docker run --rm -i -v ${workspaceFolder}:/workspace -e WORKSPACE_ROOT=/workspace -e \"FASTEDGE_API_KEY=$FASTEDGE_API_KEY\" -e \"FASTEDGE_API_URL=$FASTEDGE_API_URL\" ghcr.io/g-core/fastedge-mcp-server:latest"
       ],
       "env": {
-        "WORKSPACE_ROOT": "${workspaceFolder}",
         "FASTEDGE_API_KEY": "your_api_key_here",
         "FASTEDGE_API_URL": "https://api.preprod.world" # Optional environment setting
       }

DEVELOPMENT.md

@@ -28,14 +28,12 @@ RUN npm ci --omit=dev
 # Copy only the build output
 COPY --from=builder /app/build ./build
 
-# Create required directories
-# RUN mkdir -p /workspace/apps
-
 # Default to workspace in volumey
 ENV WORKSPACE_ROOT=/workspace
 
 # Set up a volume mount point for workspace data
 VOLUME [ "/workspace" ]
 
-# Start MCP server - use node directly for standalone execution
+# Start MCP server
 CMD ["node", "build/server.js"]
+

Dockerfile

@@ -6,11 +6,30 @@ RUN rustup target add wasm32-wasip1 && \
     rm -rf /usr/local/rustup/toolchains/*/lib/rustlib/*/test /usr/local/rustup/toolchains/*/lib/rustlib/*/examples
 
 # Install Node.js v23 using NodeSource binary distribution
+# Support multiple architectures
 RUN apt-get update && \
-    apt-get install -y --no-install-recommends curl ca-certificates xz-utils && \
-    curl -fsSL https://nodejs.org/dist/v23.5.0/node-v23.5.0-linux-x64.tar.xz -o node.tar.xz && \
+    apt-get install -y --no-install-recommends curl ca-certificates xz-utils bash && \
+    ARCH=$(dpkg --print-architecture) && \
+    case "$ARCH" in \
+        amd64) NODE_ARCH="x64" ;; \
+        arm64) NODE_ARCH="arm64" ;; \
+        *) echo "Unsupported architecture: $ARCH" && exit 1 ;; \
+    esac && \
+    curl -fsSL https://nodejs.org/dist/v23.5.0/node-v23.5.0-linux-${NODE_ARCH}.tar.xz -o node.tar.xz && \
     tar -xJf node.tar.xz -C /usr/local --strip-components=1 && \
     rm node.tar.xz && \
     apt-get purge -y xz-utils && \
     apt-get autoremove -y && \
     rm -rf /var/lib/apt/lists/* /usr/share/doc /usr/share/man /usr/share/info /tmp/*
+
+# Ensure bash is the default shell and set up proper shell environment for Windows Docker Desktop
+RUN ln -sf /bin/bash /bin/sh && \
+    echo 'export PS1="\u@\h:\w\$ "' >> /etc/bash.bashrc && \
+    echo 'export PATH=$PATH:/usr/local/bin' >> /etc/bash.bashrc
+
+# Set default shell to bash for better Windows Docker Desktop compatibility
+SHELL ["/bin/bash", "-c"]
+
+# Set environment variables for better shell experience
+ENV SHELL=/bin/bash
+ENV TERM=xterm-256color

Dockerfile-base

@@ -0,0 +1,189 @@
+# Multi-Architecture Docker Support
+
+## Overview
+
+This project now supports multi-architecture Docker images that can run on:
+
+- **Linux** (amd64, arm64)
+- **macOS** (via Docker Desktop)
+- **Windows** (via Docker Desktop with WSL2)
+
+## Architecture Support
+
+### Supported Platforms
+
+- `linux/amd64` - Standard x86_64 Linux systems
+- `linux/arm64` - ARM64 Linux systems (Apple Silicon, ARM servers)
+
+### Running on Different Platforms
+
+#### Linux
+
+```bash
+# Native support - will automatically use the correct architecture
+docker run ghcr.io/g-core/fastedge-mcp-server:latest
+```
+
+#### macOS (Intel & Apple Silicon)
+
+```bash
+# Docker Desktop automatically pulls the correct architecture
+# Intel Macs: linux/amd64
+# Apple Silicon Macs: linux/arm64
+docker run ghcr.io/g-core/fastedge-mcp-server:latest
+```
+
+#### Windows
+
+```bash
+# Docker Desktop with WSL2 backend
+docker run ghcr.io/g-core/fastedge-mcp-server:latest
+```
+
+## Building Multi-Architecture Images
+
+### Base Image
+
+The base image is built using the existing workflow:
+
+```bash
+# Use the build-docker-base-image.yaml workflow
+# Manually triggered via GitHub Actions UI or API
+```
+
+### Main Image
+
+The main application image is built using the multi-architecture base:
+
+```bash
+# Use the build-push-docker action with platforms: linux/amd64,linux/arm64
+```
+
+## Development Notes
+
+### Local Multi-Architecture Building
+
+#### Full Multi-Architecture Build (Requires Network Connectivity)
+
+For environments with proper network connectivity and ARM64 emulation:
+
+```bash
+# Set up buildx with docker-container driver (one-time setup)
+docker buildx create --name multiarch --driver docker-container --use
+docker buildx inspect --bootstrap
+
+# Build base image for multiple architectures
+docker buildx build --platform linux/amd64,linux/arm64 -f Dockerfile-base -t fastedge-mcp-server-base:latest --load .
+
+# Build main image for multiple architectures
+docker buildx build --platform linux/amd64,linux/arm64 --build-arg BASE_IMAGE=fastedge-mcp-server-base:latest -t fastedge-mcp-server:latest --load .
+```
+
+#### Single Architecture Build (Recommended for Local Development)
+
+If you encounter network issues or want faster builds:
+
+```bash
+# Use default driver (no special setup required)
+docker buildx use default
+
+# Build base image for current platform only
+docker build -f Dockerfile-base -t fastedge-mcp-server-base:latest .
+
+# Build main image for current platform
+docker build --build-arg BASE_IMAGE=fastedge-mcp-server-base:latest -t fastedge-mcp-server:latest .
+```
+
+### Architecture-Specific Considerations
+
+1. **Node.js Binaries**: The Dockerfile-base now automatically detects the target architecture and downloads the appropriate Node.js binary
+2. **Rust Compilation**: Rust toolchain supports cross-compilation for both amd64 and arm64
+3. **npm Dependencies**: Native dependencies are compiled for the target architecture during the build process
+
+### Limitations
+
+- **Windows Containers**: Not supported due to complexity and requirement for Windows hosts
+- **Performance**: ARM64 images may have slightly different performance characteristics
+- **Build Time**: Multi-architecture builds take longer due to building for multiple platforms
+
+## Troubleshooting
+
+### Platform-Specific Issues
+
+If you encounter platform-specific issues, you can force a specific architecture:
+
+```bash
+# Force amd64 on any platform
+docker run --platform linux/amd64 ghcr.io/g-core/fastedge-mcp-server:latest
+
+# Force arm64 on any platform (if available)
+docker run --platform linux/arm64 ghcr.io/g-core/fastedge-mcp-server:latest
+```
+
+### Build Issues
+
+Common issues and solutions when building multi-architecture images:
+
+#### 1. "Multi-platform build is not supported for the docker driver"
+
+**Problem**: Using the default Docker driver which doesn't support multi-platform builds.
+
+**Solution**:
+
+```bash
+# Create and use a docker-container builder
+docker buildx create --name multiarch --driver docker-container --use
+docker buildx inspect --bootstrap
+```
+
+**Alternative**: Use single-platform builds with the default driver:
+
+```bash
+docker buildx use default
+docker build -f Dockerfile-base -t fastedge-mcp-server-base:latest .
+```
+
+#### 2. Network connectivity issues (IPv6)
+
+**Problem**: `dial tcp [IPv6]:443: connect: network is unreachable`
+
+**Solutions**:
+
+```bash
+# Option 1: Use default driver (often has better network compatibility)
+docker buildx use default
+docker build -f Dockerfile-base -t fastedge-mcp-server-base:latest .
+
+# Option 2: Configure Docker daemon to prefer IPv4
+# Edit /etc/docker/daemon.json:
+# {
+#   "ipv6": false,
+#   "dns": ["8.8.8.8", "8.8.4.4"]
+# }
+# Then: sudo systemctl restart docker
+
+# Option 3: Use Docker registry mirrors
+# Add --registry-mirror flag or configure in daemon.json
+```
+
+#### 3. "No output specified with docker-container driver"
+
+**Problem**: Warning about build results only staying in cache.
+
+**Solution**: Always specify output with `--load` or `--push`:
+
+```bash
+# Load into local Docker images
+docker buildx build --platform linux/amd64,linux/arm64 -f Dockerfile-base -t fastedge-mcp-server-base:latest --load .
+
+# Push to registry (for CI/CD)
+docker buildx build --platform linux/amd64,linux/arm64 -f Dockerfile-base -t fastedge-mcp-server-base:latest --push .
+```
+
+#### 4. General troubleshooting
+
+- Check buildx status: `docker buildx ls`
+- Verify builder capabilities: `docker buildx inspect`
+- Ensure base images support target architectures
+- Test single-platform builds first
+- Use `--progress=plain` for detailed build output