Help

Troubleshooting & cleanup

Dashcam is the lightest-weight workshop in this repo — one scenario, no reactive/proactive pair, and (in Option A) a Docker image with everything baked in — so most failure modes come down to the image not being rebuilt or the wrong working directory.

Troubleshooting

"name already in use" on docker run --name casky-dashcam

Not broken — setup already succeeded once. Either reuse the existing container (skip straight to ./verify.sh) or run ./cleanup.sh first.

A bare AnalyzerEngine() seems to hang or downloads ~400MB

That's spaCy auto-downloading en_core_web_lg, Presidio's own packaged default — this is patched at docker build time in Option A's image to use the small model already baked in, so it shouldn't happen there. If you're on Option B (local Python) and see this, you're hitting the same footgun the SKILL.md's own quickstart has; point the analyzer at en_core_web_sm explicitly, see Option B's callout.

Commands fail with "no such file" / "no matches found"

Almost always a wrong working directory. Every command on the Setup page assumes you're in casky-workshops/dashcam/:

docker exec casky-dashcam test -f /root/dashcam/verify.sh \
  && echo "[+] mount OK" || echo "[!] wrong directory — re-run from casky-workshops/dashcam/"

Invalid API key inside the Kali container

casky-box/.env writes values as ANTHROPIC_API_KEY="sk-ant-..." (quoted) — docker run --env-file does not strip quotes. Re-run the sed fix on the Setup page and confirm with grep -c '^sk-ant-' before retrying.

verify.sh fails on the image-redaction check

That check just confirms data/dashcam-frame-0417.png opens and has the expected size via Pillow — if it fails, data/ likely got modified mid-exercise; run ./reset.sh to restore it from .pristine/.

Cleanup

./cleanup.sh removes everything a run of this exercise creates: the casky-dashcam container (Option A), and the local venv plus cloned upstream skills repo (Option B). Safe to re-run.

./cleanup.sh                # container + venv + cloned upstream skills repo
./cleanup.sh --keep-venv    # keep the venv, only remove the container + cloned skills repo
./cleanup.sh --with-image   # also remove the casky-dashcam image

data/, skills/, and the scenario scripts are untouched by cleanup — use ./reset.sh if data/ got modified mid-exercise and you want it restored from .pristine/.

Authorized & lawful use only. All data is synthetic and self-contained.