vscode-docs/remote-release-notes/v1_70.md

2.6 KiB

July 2022 (version 1.70)

Development Containers

We continue work across the Dev Containers extension and the open dev container specification, which seeks to allow anyone in any tool (including ones other than VS Code) to use containers for their inner and outer loop activities. Its reference implementation is the dev container CLI.

Container lifecycle diagram

Dev container Features

Dev container Features are a preview option of dev containers consisting of self-contained units of installation code and configuration. We've been iterating on our initial Features implementation, and the latest has been merged into the spec repo and the dev container CLI.

We've also merged an updated proposal for distributing features and templates, now with the ability to upload them as OCI Artifacts in registries. We are working toward getting this into the CLI, and we welcome any feedback on the proposal via GitHub Issues or Discussions.

Dev container CLI

The CLI now supports multiple --image-name parameters, such as:

devcontainer build --workspace-folder ./ --image-name alpine3 --image-name alpine3.0

This allows you to tag the same image more than once, which is especially helpful for tagging images with multiple registries.

We've added the ability to test features from the CLI with devcontainer features test. Below is an example of this command:

Terminal output of devcontainer features test

There was also a bug fix to allow falling back to id -u -n in the case when the container can't find a username.

Dev Containers

We made a fix so that copying a file with executable permissions (such as the dev container CLI executable) preserves the executable bit on the file permissions.

The latest in dev container features and the CLI will also be landing in Dev Containers in the coming week.