feat(cli): add --docker-path flag to read-configuration command#245
Conversation
✅ Deploy Preview for devsydev canceled.
|
|
Warning Rate limit exceeded
To continue reviewing without waiting, purchase usage credits in the billing tab. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Allow users to specify a custom docker/podman executable path when reading configuration from a running container via --container-id. Previously the command hardcoded "docker" — this aligns it with the exec command which already supports --docker-path.
cd4b750 to
a1c589c
Compare
Summary
Adds
--docker-pathflag to theread-configurationcommand, allowing users to specify a custom docker/podman executable path when reading configuration from a running container via--container-id. Previously the command hardcoded"docker"as the container runtime binary. This alignsread-configurationwith theexeccommand which already supports--docker-path.Per the devcontainer CLI reference spec, the
read-configurationcommand supports--docker-pathas an optional flag for specifying the Docker CLI path (or Docker-compatible CLI) to use.Changes:
DockerPathfield toReadConfigurationCmdstruct--docker-pathflag inNewReadConfigurationCmd()following the same pattern ascmd/exec.goresolveConfigFromContainer()to use the custom docker path when specified (defaults to "docker" if empty)--docker-pathusage, and invalid--docker-patherror