Reset local state — wipe stores
Goal
You will wipe local durable state for a JARVIS dev stack (Run Store, Event Stream, Artifact Store, Node Registry DB).
When to use this
- You want a clean slate for testing.
- You are debugging a “works on my machine” issue caused by old DB files or artifacts.
Prerequisites
- Docker + Docker Compose
- You are running the stack via
JARVIS_Release(typically witharp-jarvis stack) - You understand this is destructive (it deletes local volumes).
Steps
-
Stop the stack and delete volumes:
cd JARVIS_Release
arp-jarvis stack down --volumes -
(Optional) Remove any dangling images built locally:
docker image prune -f
Verify
docker volume lsno longer shows the JARVIS volumes (or they have been recreated after the nextup).
Troubleshooting
compose/.env.localnot found → you didn’t create it yet →cp compose/.env.example compose/.env.local.- “volume is in use” → containers are still running →
arp-jarvis stack psthen stop them, ordocker psand stop manually. - You only want to wipe one store (not all) → don’t use
-v; remove the specific volume by name withdocker volume rm <name>.
Cleanup / Rollback
- None. This is the rollback.
Next steps
- Concept: Artifacts and replay
- Reference: JARVIS internal services
- How-to: Run JARVIS locally (dev mode)