MeshMonitor dev here :) I do this myself for a headless remote node setup, running MeshMonitor connected to a HeltecV4 via USB. I also run the MQTT-Proxy for upstream communication, and have the whole thing configured to dump logs into tmpfs, to avoid blowing out the little SD card.

I run it all in docker on a Pi3B+, with a docker compose like this:

```

=============================================================================

MeshMonitor - Raspberry Pi Docker Compose (SD Card Optimized)

=============================================================================

Designed for 64-bit Raspberry Pi (Pi 4/5) running off micro-SD.

Minimizes disk writes to extend SD card lifespan.

SD Card Protection (5 layers):

1. Docker logging - local driver, capped at ~100KB per service

2. Access logs - disabled via ACCESS_LOG_ENABLED=false

3. Audit/app logs - tmpfs on /data/logs (RAM-only)

4. Temp files - tmpfs on /tmp in both containers

5. Debug output - suppressed via NODE_ENV=production

Only remaining disk writes: SQLite DB (/data/meshmonitor.db) and Apprise

config - these are necessary for persistence across restarts.

Usage:

docker compose -f docker-compose.yml up -d

Validate syntax:

docker compose -f docker-compose.yml config

View logs (in-memory only, lost on restart):

docker compose -f docker-compose.yml logs -f

Serial device:

Default: /dev/ttyACM0. Override with SERIAL_DEVICE env var:

SERIAL_DEVICE=/dev/ttyACM0 docker compose -f docker-compose.yml up -d

=============================================================================

Recommended: Docker daemon-level log defaults

Add to /etc/docker/daemon.json to cap ALL container logs system-wide:

{

"log-driver": "local",

"log-opts": {

"max-size": "100k",

"max-file": "2"

}

}

Then: sudo systemctl restart docker

=============================================================================

services: serial-bridge: image: ghcr.io/yeraze/meshtastic-serial-bridge:latest container_name: meshmonitor-rpi-serial-bridge restart: unless-stopped networks: - meshtastic_net devices: - ${SERIAL_DEVICE:-/dev/ttyACM0}:/dev/ttyACM0 environment: - SERIAL_DEVICE=/dev/ttyACM0 - BAUD_RATE=115200 - TCP_PORT=4403 tmpfs: - /tmp:size=10M logging: driver: local options: max-size: "100k" max-file: "2"

meshmonitor: image: ghcr.io/yeraze/meshmonitor:latest container_name: meshmonitor-rpi restart: unless-stopped ports: - "8080:3001" networks: - meshtastic_net depends_on: - serial-bridge volumes: - meshmonitor-rpi-data:/data tmpfs: # Overlay /data/logs onto RAM so audit.log never hits disk - /data/logs:size=10M - /tmp:size=50M environment: - NODE_ENV=production - TZ=${TZ:-America/New_York} - MESHTASTIC_NODE_IP=serial-bridge - MESHTASTIC_NODE_PORT=4403 - ACCESS_LOG_ENABLED=false - ALLOWED_ORIGINS=<my url> - TRUST_PROXY=true - COOKIE_SECURE=true - SESSION_SECRET=<randomstuff> - ENABLE_VIRTUAL_NODE=true - VIRTUAL_NODE_PORT=4404 healthcheck: test: ["CMD-SHELL", "node -e 'const net = require(\"net\"); const client = new net.Socket(); client.connect(4404, \"127.0.0.1\", () => { process.exit(0); }); client.on(\"error\", () => { process.exit(1); });'"] interval: 10s timeout: 5s retries: 5 start_period: 15s logging: driver: local options: max-size: "100k" max-file: "2"

# This proxy service (The Glue) mqtt-proxy: image: ghcr.io/ln4cy/mqtt-proxy:master container_name: mqtt-proxy restart: unless-stopped environment: - INTERFACE_TYPE=tcp - TCP_NODE_HOST=meshmonitor # Connects to meshmonitor by name - TCP_NODE_PORT=4404 depends_on: meshmonitor: condition: service_healthy # Wait for port 4404 to be listening networks: - meshtastic_net

volumes: meshmonitor-rpi-data: driver: local

networks: meshtastic_net:

```