Describe the bug
When Copilot CLI proposes or runs a command that accesses a path inside a Docker container, it appears to treat that path as if it were a local host path and triggers a directory access approval prompt for it.
docker compose exec <service> ls /some/container/path/file
triggers a permission prompt claiming that /some/container/path/file is outside the allowed local directories. And asks if it should default allow it. Here im unsere what this will mean and in what context this will be added.
Otherwise thanks a lot for the great product!
Affected version
GitHub Copilot CLI 1.0.11
Steps to reproduce the behavior
- start copilot without any arguments
- copilot suggest to do something with docker exec with a /path/to/somewhere
Expected behavior
No response
Additional context
No response
Describe the bug
When Copilot CLI proposes or runs a command that accesses a path inside a Docker container, it appears to treat that path as if it were a local host path and triggers a directory access approval prompt for it.
docker compose exec <service> ls /some/container/path/filetriggers a permission prompt claiming that /some/container/path/file is outside the allowed local directories. And asks if it should default allow it. Here im unsere what this will mean and in what context this will be added.
Otherwise thanks a lot for the great product!
Affected version
GitHub Copilot CLI 1.0.11
Steps to reproduce the behavior
Expected behavior
No response
Additional context
No response