|
14 | 14 | | *Works in Codespaces* | Yes |
|
15 | 15 | | *Container host OS support* | Linux, macOS, Windows |
|
16 | 16 | | *Container OS* | Ubuntu |
|
17 |
| -| *Languages, platforms* | Python, Node.js, JavaScript, TypeScript, C++, Java, C#, F#, .NET Core, PHP, PowerShell, Go, Ruby, Rust | |
| 17 | +| *Languages, platforms* | Python, Node.js, JavaScript, TypeScript, C++, Java, C#, F#, .NET Core, PHP, PowerShell, Go, Ruby, Rust, Conda | |
18 | 18 |
|
19 | 19 | See **[history](history)** for information on the contents of published images.
|
20 | 20 |
|
@@ -62,11 +62,16 @@ This container also includes a running SSH server that you can use to access the
|
62 | 62 |
|
63 | 63 | That's it! Use similar arguments to those in step 5 when executing `scp` or configuring SSHFS.
|
64 | 64 |
|
| 65 | +## Using Conda |
| 66 | +This dev container and its associated image includes [the `conda` package manager](https://aka.ms/vscode-remote/conda/about). Additional packages installed using Conda will be downloaded from Anaconda or another repository if you configure one. To reconfigure Conda in this container to access an alternative repository, please see information on [configuring Conda channels here](https://aka.ms/vscode-remote/conda/channel-setup). |
| 67 | + |
| 68 | +Access to the Anaconda repository is covered by the [Anaconda Terms of Service](https://aka.ms/vscode-remote/conda/terms), which may require some organizations to obtain a commercial license from Anaconda. **However**, when this dev container or its associated image is used with GitHub Codespaces or GitHub Actions, **all users are permitted** to use the Anaconda Repository through the service, including organizations normally required by Anaconda to obtain a paid license for commercial activities. Note that third-party packages may be licensed by their publishers in ways that impact your intellectual property, and are used at your own risk. |
| 69 | + |
65 | 70 | ## Using this definition
|
66 | 71 |
|
67 | 72 | While the definition itself works unmodified, you can also directly reference pre-built versions of `.devcontainer/Dockerfile` by using the `image` property in `.devcontainer/devcontainer.json` or updating the `FROM` statement in your own `Dockerfile` to:
|
68 | 73 |
|
69 |
| -`mcr.microsoft.com/vscode/devcontainers/universal:linux` |
| 74 | +`mcr.microsoft.com/vscode/devcontainers/universal:1-linux` |
70 | 75 |
|
71 | 76 | Alternatively, you can use the contents of the `Dockerfile` to fully customize your container's contents or to build it for a container host architecture not supported by the image.
|
72 | 77 |
|
|
0 commit comments