cli icon indicating copy to clipboard operation
cli copied to clipboard

A reference implementation for the specification that can create and configure a dev container from a devcontainer.json.

Results 298 cli issues
Sort by recently updated
recently updated
newest added

When using this CLI, the container or remote user's UID and GID are not updated. This issue is documented in https://github.com/microsoft/vscode-remote-release/issues/10030, but I think the core issue might be located...

info-needed

When running `devcontainer read-configuration --include-merged-configuration --log-format json --workspace-folder ../workspace 2>/dev/null > server/configuration.json` as suggested in the example usage folder, it outputs logs in json format, then at the end, the...

info-needed

Issue https://github.com/containers/podman/issues/23055 outlines that `podman` doesn't search the local repository for the dynamically built image. This could be fixed by prefixing the dynamically generated image with `localhost/`. Container images should...

Right now it seems the only way to start a dev container is to have cloned a repository and then pass the `--workspacefolder` to each invocation of `devcontainer`. Would it...

feature-request

Features that come from registries with explicit port numbers are sometimes ignored, with only the last one remaining. For example, if devcontainer.json contains ```json "features": { "localhost:5000/name/repo/feature1:1": {}, "localhost:5000/name/repo/feature2:1": {}...

bug

https://github.com/devcontainers/cli/pull/460 is adding in support for [docker credential helpers](https://docs.docker.com/engine/reference/commandline/login/#credential-helper-protocol). There's existing test coverage on the "simpler" auth mechanisms but not on all. This likely means utlizing runners for macOS, linux,...

debt

ref: https://github.com/devcontainers/feature-starter/issues/31

debt

I :heart: the tool thanks for creating it. I observed that test containers don't stop and removed after every completion of tests. After a successful run: ``` 🏃 Starting test(s)......

feature-request

ref: https://github.com/devcontainers/spec/issues/178 This makes it difficult to use the test commands for folks that would like to developer features in a one-per-repo kind of manner

feature-request