[Request]: aliases to enable devcontainer/cli builds using container
- Dominant language
- Swift
- Stars
- 49.9k
- Forks
- 1.8k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 22
Description
### Feature or enhancement request details
It would be nice if one could use [`devcontainers/cli`](https://github.com/devcontainers/cli) + `container` to build dev containers on macOS. However, if one calls
```shell
devcontainer build \
--docker-path container \
--workspace-folder .
```
it fails with
```log
Error: Plugin 'container-pull' not found.
- If system services are not running, start them with: container system start
- If the plugin isn't installed, ensure it exists under:
Check to see that the plugin exists under:
- /usr/local/libexec/container-plugins/pull
- /usr/local/libexec/container/plugins/pull
Usage: container [--debug]
See 'container --help' for more information.
[208 ms] Retrying (Attempt 0) with error
'Command failed: container pull rust:1.98.0-trixie@sha256:620dbcd124499c59e2406d3741574b5c5838cf9eb9656f0c3a03948f79b02959
'
Error: Plugin 'container-pull' not found.
- If system services are not running, start them with: container system start
- If the plugin isn't installed, ensure it exists under:
Check to see that the plugin exists under:
- /usr/local/libexec/container-plugins/pull
- /usr/local/libexec/container/plugins/pull
Usage: container [--debug]
See 'container --help' for more information.
```
Some aliases, e.g., `container pull` ➡️ `container image pull`, could make this possible.
### Code of Conduct
- [x] I agree to follow this project's Code of Conduct
Contributor guide
Research direction
Start by reproducing the devcontainer build command with --docker-path container and --workspace-folder ., then inspect how the container pull command is resolved. The requested behavior is for aliases such as container pull to reach container image pull so the devcontainers/cli build completes successfully on macOS.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos
- Domain
- cli, devtools
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100