v0.2.2

v0.2.2 — Log rotation + post-update hook fix

A maintenance release prompted by an operator whose 115G pi disk filled to 100%, traced to a single 60GB Docker log file on logos-node. Fixes both the immediate cause (no log caps) and the related delivery gap (post-update hooks were silently dead).

What you get

• Log size caps on every container. Compose generators now emit logging: blocks. Total log ceiling across the full stack (node + exporter + otel + prometheus + grafana) is capped at ~490MB instead of unbounded.

  • logos-node: 50MB × 5 files = 250MB
  • monitoring services: 20MB × 3 files = 60MB each

• logos-node update now actually applies changes. Previously, after pulling new CLI code the re-exec dropped state, so the post-update block (compose regen + monitoring rebuild prompt) never ran. Fixed by passing the changed-files list through the re-exec env. The existing monitoring auto-rebuild logic now fires correctly too.

• Auto-regenerate docker-compose.yml on schema changes. When an update touches lib/docker.sh or docker/, the on-disk compose is regenerated and you're prompted to recreate the container.

Upgrade

logos-node update

That's it — the new flow regenerates the compose and offers to recreate the container in one go. Caps apply automatically once the container is recreated.

Reclaiming space if your disk is already full

If you're hitting the same 100% disk issue, do this first (existing logs aren't truncated by adding a cap):

logos-node stop                                                                                                                                                                   
logos-node monitor stop                                   
                                                                                                                                                                                  
# Truncate existing Docker logs in place (json-file driver)                                                                                                                       
sudo find /var/lib/docker/containers/ -type f -name "*-json.log*" \                                                                                                               
  -exec truncate -s 0 {} \;                                                                                                                                                       
                                                                                                                                                                                  
# Reclaim build cache + unused images                                                                                                                                             
docker builder prune -af                                                                                                                                                          
docker image prune -af                                    

df -h /                    # verify space freed                                                                                                                                   
logos-node update          # pull v0.2.2 + regen compose
logos-node start           # bring up with the new caps                                                                                                                           
                                                                                                                                                                                  
Verify after restart:                                                                                                                                                             
docker inspect logos-node | grep -A5 LogConfig                                                                                                                                    
# Should show: max-size 50m, max-file 5                   

Compatibility

• No breaking changes — Logos Blockchain still pinned at 0.1.2
• No reset required; just logos-node update and accept the recreate prompt

Full Changelog: v0.2.1...v0.2.2