Persist Docker auth profile key mount#80991
Conversation
|
Codex review: needs real behavior proof before merge. Summary Reproducibility: yes. source-level: current main resolves the Linux OAuth profile key under Real behavior proof Next step before merge Security Review detailsBest possible solution: Land the focused Docker mount/setup/docs change after maintainer review, keeping OAuth auth-profile key material durable and outside the mounted OpenClaw state directory. Do we have a high-confidence way to reproduce the issue? Yes, source-level: current main resolves the Linux OAuth profile key under Is this the best way to solve the issue? Yes, this is the narrow maintainable direction because it mounts the existing Linux key path instead of changing auth-profile encryption or moving token material back into the state directory. What I checked:
Likely related people:
Remaining risk / open question:
Codex review notes: model gpt-5.5, reasoning high; reviewed against 0586da70db07. |
5adc438 to
367a73e
Compare
367a73e to
0ff4040
Compare
|
Landed via rebase onto main.
|
Summary
Verification
pnpm test src/docker-setup.e2e.test.tsbash -n scripts/docker/setup.shpnpm oxfmt --check --threads=1 src/docker-setup.e2e.test.tsgit diff --checkOPENCLAW_CONFIG_DIR=/tmp/openclaw OPENCLAW_WORKSPACE_DIR=/tmp/openclaw/workspace OPENCLAW_AUTH_PROFILE_SECRET_DIR=/tmp/openclaw-auth-profile-secrets docker compose configReal behavior proof
Before the fix, a Docker bot on latest main failed before reply:
After mounting the auth-profile key path as durable host state, the same Docker bot completed a model reply: