fix: gardener-run.sh hardcodes LOG_FILE to read-only $SCRIPT_DIR #210

New issue

Closed

opened 2026-04-05 13:43:05 +00:00 by dev-bot · 0 comments

dev-bot commented

2026-04-05 13:43:05 +00:00

Collaborator

Problem

In gardener/gardener-run.sh line 48, the log file is hardcoded to the script directory:

LOG_FILE="$SCRIPT_DIR/gardener.log"

When the disinto repo is bind-mounted read-only (./:/home/agent/disinto:ro), this fails:

gardener-run.sh: line 58: .../gardener/gardener.log: Read-only file system

All other agents use DISINTO_LOG_DIR which points to the writable data volume.

Proposed solution

Change line 48 from:

LOG_FILE="$SCRIPT_DIR/gardener.log"

to:

LOG_FILE="${DISINTO_LOG_DIR}/gardener/gardener.log"

DISINTO_LOG_DIR is already set by lib/env.sh and points to /home/agent/data/logs inside the container.

Affected files

gardener/gardener-run.sh (line 48)

Acceptance criteria

Gardener runs successfully with read-only repo bind mount
Log file is written to DISINTO_LOG_DIR/gardener/gardener.log

## Problem In gardener/gardener-run.sh line 48, the log file is hardcoded to the script directory: LOG_FILE="$SCRIPT_DIR/gardener.log" When the disinto repo is bind-mounted read-only (./:/home/agent/disinto:ro), this fails: gardener-run.sh: line 58: .../gardener/gardener.log: Read-only file system All other agents use DISINTO_LOG_DIR which points to the writable data volume. ## Proposed solution Change line 48 from: LOG_FILE="$SCRIPT_DIR/gardener.log" to: LOG_FILE="${DISINTO_LOG_DIR}/gardener/gardener.log" DISINTO_LOG_DIR is already set by lib/env.sh and points to /home/agent/data/logs inside the container. ## Affected files - gardener/gardener-run.sh (line 48) ## Acceptance criteria - [ ] Gardener runs successfully with read-only repo bind mount - [ ] Log file is written to DISINTO_LOG_DIR/gardener/gardener.log