Skip to content

fix(docker): move persistent data under tinyagi user home directory#265

Merged
jlia0 merged 1 commit intomainfrom
jlia0/fix-codex-system-prompt
Mar 26, 2026
Merged

fix(docker): move persistent data under tinyagi user home directory#265
jlia0 merged 1 commit intomainfrom
jlia0/fix-codex-system-prompt

Conversation

@jlia0
Copy link
Copy Markdown
Collaborator

@jlia0 jlia0 commented Mar 26, 2026

Description

Move all persistent data from /data to /home/tinyagi so the Docker volume covers both app data and AI CLI state. AI CLIs (codex, claude-code) store config under $HOME (~/.codex/, ~/.claude/), which was /home/tinyagi — outside the previous /data volume mount. This caused codex shell snapshot failures and lost CLI config across container restarts.

Changes

  • Update Dockerfile to create persistent dirs under /home/tinyagi instead of /data
  • Update docker-compose.yml volume mount from /data to /home/tinyagi
  • Update docker-entrypoint.sh paths and default settings to use /home/tinyagi

Testing

  • Rebuild Docker image and verify codex agent invocation no longer produces shell snapshot errors
  • Verify persistent data survives container restarts

Checklist

  • PR title follows conventional commit format (type(scope): description)
  • I have tested these changes locally
  • My changes don't introduce new warnings or errors
  • I have updated documentation if needed

AI CLIs (codex, claude-code) store config/state under $HOME (~/.codex/,
~/.claude/), which was /home/tinyagi — outside the /data volume mount.
This caused codex shell snapshot failures and lost config across restarts.
Move all persistent data from /data to /home/tinyagi so the volume
covers both app data and CLI state.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant