|
9 | 9 | | *Categories* | Core, Languages | |
10 | 10 | | *Image type* | Dockerfile | |
11 | 11 | | *Published image* | mcr.microsoft.com/devcontainers/typescript-node | |
12 | | -| *Available image variants* | 24 / 24-bookworm, 22 / 22-bookworm, 20 / 20-bookworm, 24-bullseye, 22-bullseye, 20-bullseye ([full list](https://mcr.microsoft.com/v2/devcontainers/typescript-node/tags/list)) | |
| 12 | +| *Available image variants* | 24 /24-trixie, 22 / 22-trixie, 20 / 20-trixie, 24-bookworm, 22-bookworm, 20-bookworm, 24-bullseye, 22-bullseye, 20-bullseye ([full list](https://mcr.microsoft.com/v2/devcontainers/typescript-node/tags/list)) | |
13 | 13 | | *Published image architecture(s)* | x86-64, arm64/aarch64 for `bookworm`, and `bullseye` variants | |
14 | 14 | | *Container host OS support* | Linux, macOS, Windows | |
15 | 15 | | *Container OS* | Debian | |
|
20 | 20 | You can directly reference pre-built versions of `Dockerfile` by using the `image` property in `.devcontainer/devcontainer.json` or updating the `FROM` statement in your own `Dockerfile` to one of the following. An example `Dockerfile` is included in this repository. |
21 | 21 |
|
22 | 22 | - `mcr.microsoft.com/devcontainers/typescript-node` (latest) |
23 | | -- `mcr.microsoft.com/devcontainers/typescript-node:24` (or `24-bookworm`, `24-bullseye` to pin to an OS version) |
24 | | -- `mcr.microsoft.com/devcontainers/typescript-node:22` (or `22-bookworm`, `22-bullseye` to pin to an OS version) |
25 | | -- `mcr.microsoft.com/devcontainers/typescript-node:20` (or `20-bookworm`, `20-bullseye` to pin to an OS version) |
| 23 | +- `mcr.microsoft.com/devcontainers/typescript-node:24` (or `24-trixie`, `24-bookworm`, `24-bullseye` to pin to an OS version) |
| 24 | +- `mcr.microsoft.com/devcontainers/typescript-node:22` (or `22-trixie`, `22-bookworm`, `22-bullseye` to pin to an OS version) |
| 25 | +- `mcr.microsoft.com/devcontainers/typescript-node:20` (or `20-trixie`, `20-bookworm`, `20-bullseye` to pin to an OS version) |
26 | 26 |
|
27 | 27 | Refer to [this guide](https://containers.dev/guide/dockerfile) for more details. |
28 | 28 |
|
29 | 29 | You can decide how often you want updates by referencing a [semantic version](https://semver.org/) of each image. For example: |
30 | 30 |
|
31 | | -- `mcr.microsoft.com/devcontainers/typescript-node:3-24` (or `3-24-bookworm`, `3-24-bullseye`) |
32 | | -- `mcr.microsoft.com/devcontainers/typescript-node:3.0-24` (or `3.0-24-bookworm`, `3.0-24-bullseye`) |
33 | | -- `mcr.microsoft.com/devcontainers/typescript-node:3.0.2-24` (or `3.0.2-24-bookworm`, `3.0.2-24-bullseye`) |
| 31 | +- `mcr.microsoft.com/devcontainers/typescript-node:4-24` (or `4-24-trixie`, `4-24-bookworm`, `4-24-bullseye`) |
| 32 | +- `mcr.microsoft.com/devcontainers/typescript-node:4.0-24` (or `4.0-24-trixie`, `4.0-24-bookworm`, `4.0-24-bullseye`) |
| 33 | +- `mcr.microsoft.com/devcontainers/typescript-node:4.0.0-24` (or `4.0.0-24-trixie`, `4.0.0-24-bookworm`, `4.0.0-24-bullseye`) |
34 | 34 |
|
35 | 35 | However, we only do security patching on the latest [non-breaking, in support](https://github.com/devcontainers/images/issues/90) versions of images (e.g. `3-24`). You may want to run `apt-get update && apt-get upgrade` in your Dockerfile if you lock to a more specific version to at least pick up OS security updates. |
36 | 36 |
|
|
0 commit comments