Current behavior
PipeStep runs containers as root with read-write source mounts. For a debugging tool running on your own code, the threat model is similar to docker run -v $(pwd):/workspace -it ubuntu bash — which most developers do regularly.
Proposed improvements
--read-only flag to mount source as read-only (prevent accidental modifications during debugging)- Non-root user mapping option
- Optional network isolation (
--network none) for offline debugging
Implementation notes
The engine is ~120 lines (pipestep/engine.py). These are straightforward Docker SDK flags. PRs welcome — this is a good first contribution.
Priority
Medium. This matters more as PipeStep moves toward team/CI-environment usage (see #1). For local solo debugging, current behavior is acceptable.
Current behavior
PipeStep runs containers as root with read-write source mounts. For a debugging tool running on your own code, the threat model is similar to
docker run -v $(pwd):/workspace -it ubuntu bash— which most developers do regularly.Proposed improvements
--read-onlyflag to mount source as read-only (prevent accidental modifications during debugging)--network none) for offline debuggingImplementation notes
The engine is ~120 lines (
pipestep/engine.py). These are straightforward Docker SDK flags. PRs welcome — this is a good first contribution.Priority
Medium. This matters more as PipeStep moves toward team/CI-environment usage (see #1). For local solo debugging, current behavior is acceptable.