Help
Troubleshooting & cleanup
Same failure modes as every other exercise in this repo — this one reuses the identical Kali-container/Casky-Box pattern, just with different container and evidence-file names, and no pcap tooling to worry about.
Troubleshooting
Not broken — setup already succeeded once. Either reuse the existing container (skip
straight to ./verify.sh) or run ./cleanup.sh first.
This happens at docker build time (baked into the image) — only
relevant if you're rebuilding rather than pulling from GHCR. Just re-run the build,
Docker's layer cache means everything before that RUN step is skipped:
docker build -t casky-fastlane .
Almost always a wrong working directory. Every command on the Setup page assumes you're in
casky-workshops/fastlane/:
# Section 1 (inside the Kali container)
docker exec casky-fastlane test -f /root/fastlane/verify.sh \
&& echo "[+] mount OK" || echo "[!] wrong directory — re-run from casky-workshops/fastlane/"
# Section 2 (on the host, before copying evidence)
test -f app/rls-policies.json && echo "[+] correct folder" || echo "[!] cd to casky-workshops/fastlane first"
The quoted-value bug — see Section 1 prerequisites.
Re-run the sed fix and confirm with grep -c '^sk-ant-' before
retrying.
That's a casky-box issue, not a FastLane/SpeedBump one — see that folder's own README troubleshooting section.
Cleanup
./cleanup.sh removes everything a run of this exercise creates outside the
fastlane/ folder: the casky-fastlane container and any evidence files
copied into casky-box/evidence/. Safe to re-run.
./cleanup.sh # container + copied evidence
./cleanup.sh --casky-box-path ../casky-box # if casky-box/ was moved elsewhere
./cleanup.sh --with-image # also remove the casky-fastlane image
It does not touch Casky Box's own containers (casky-runner,
casky-db, casky-ui), and doesn't delete Postgres investigation
records — those are history, not litter.
If the evidence files get modified mid-exercise, restore them with:
docker exec -w /root/fastlane casky-fastlane ./reset.sh
Authorized & lawful use only. All data is synthetic and self-contained; no live systems are touched.