Yeraze/meshmonitor v1.11.2

v1.11.2 - Protobuf Submodule Docker Fix

on GitHub

🐛 Bug Fix Release

Fixed: Docker Build Missing Protobufs (#86)

Issue: Docker builds were failing with ENOENT: no such file or directory, open '/app/protobufs/meshtastic/mesh.proto'

Root Cause: The protobufs git submodule was not being initialized during GitHub Actions Docker builds, resulting in empty protobuf directories in published images.

✅ What's Fixed

• GitHub Actions Workflows: All Docker build workflows now properly checkout git submodules

  • docker-publish.yml
  • release.yml
  • ci.yml

• Dockerfile: Added verification check to fail fast if protobufs are missing with clear error message

• Documentation: Updated README.md with proper git clone instructions using --recurse-submodules

📦 Docker Images

Published Docker images now correctly include all required protobuf definitions and will work properly.

🚀 Quick Start

# Using Docker (recommended)
docker pull ghcr.io/yeraze/meshmonitor:v1.11.2

# Building from source
git clone --recurse-submodules https://github.com/Yeraze/meshmonitor.git
cd meshmonitor
docker compose up -d

🔧 For Existing Clones

If you already cloned without submodules:

git submodule update --init --recursive

Full Changelog: v1.11.1...v1.11.2

🚀 MeshMonitor v1.11.2

📦 Installation

Docker (recommended):

docker run -d \
  --name meshmonitor \
  -p 8080:3001 \
  -v meshmonitor-data:/data \
  ghcr.io/Yeraze/meshmonitor:v1.11.2

🧪 Testing

✅ All tests passed
✅ TypeScript checks passed
✅ Docker images built for linux/amd64, linux/arm64, linux/arm/v7

📋 Changes

See commit history for detailed changes.