cli
cli copied to clipboard
A reference implementation for the specification that can create and configure a dev container from a devcontainer.json.
When working with dev containers locally (e.g. in Visual Studio Code), it can be productive to mount host folders in the container (e.g. `.azure` to share login credentials into the...
Maybe related to devcontainers/spec#18 Currently the only way to set labels seems to be to write to Dockerfiles or compose files, but if we store images in the registry, we...
I was getting kind of tired of opening a new VS Code window and using the "Remote-Containers: Open Folder in Container..." command and was wondering if there was an easy...
Recently Codespaces has gotten several reports where the root cause was difficult to debug. It would be useful if the logs emitted from the CLI clearly mark the start and...
Now that we have a public `devcontainers/features` repo, we should replace all tests that reference earlier, test repos.
As [best practice](https://docs.docker.com/develop/develop-images/dockerfile_best-practices/#user), non-root users are created as system users without a home folder. `updateUID.Dockerfile` will fail when used with such images, because it tries to chown the non-existing home...
In my env, developer will likely want to run devcontainer exec bash and then be able to navigate the container and do stuff within using command-line interface. As such, I...
Fixes #109. We could either skip chowning or create the home folder. I find the latter to be more useful because otherwise vscode will complain it can't create stuff in...
The specification includes port attributes, but the dev container CLI doesn't include port forwarding support.
Currently the dev container CLI `exec` command runs as the `remoteUser` specified in the dev container metadata. While this makes sense as a default, implementers will also need to perform...