Remote-Containers release notes

remote-release-notes/images/1_45/containers-wsl2-support.png

@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2d10f996faf8e5ac2611f68ed7a03ed40368ea56c5c226b6182f08419a1874c9
+size 385988

remote-release-notes/v1_45.md

@@ -12,5 +12,28 @@ When adding a development container configuration for a workspace using the **Re
 
 ![Add Container Configurations](images/1_45/add-configuration.png)
 
+### WSL 2 Support
+
+Remote-Containers now supports the WSL 2 based engine of Docker Desktop for Windows. You can author your `devcontainer.json` in WSL 2 using the Remote-WSL extension and then reopen the WSL 2 folder in a container:
+
+![Reopen in Container for WSL 2](images/1_45/containers-wsl2-support.png)
+
+This currently requires Windows Insiders build 18917 or later (slow ring will do), [WSL 2](https://docs.microsoft.com/en-us/windows/wsl/wsl2-install) and Docker Desktop for Windows' Edge version for its [WSL 2 based engine](https://docs.docker.com/docker-for-windows/wsl-tech-preview/).
+
+### Podman Support
+
+On Linux we now support Podman as the container engine. Simply create a symlink `docker` to the Podman executable on the `PATH`.
+
+Make sure you have `conmon` >= 2.0.14 installed to get the fix for [containers/libpod#5046](https://github.com/containers/libpod/issues/5046).
+
+### Additional devcontainer.json variables
+
+There are three additional variables for the `devcontainer.json`:
+
+| Variable | Description |
+|----------|----------------------|
+| `${localWorkspaceFolderBasename}` | Name of the local folder that was opened in VS Code (that contains `.devcontainer/devcontainer.json`). |
+| `${containerWorkspaceFolder}` | The path where the workspaces files can be found in the container. |
+| `${containerWorkspaceFolderBasename}` | Name of the folder where the workspace files can be found in the container. |
 
 ## WSL