You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
> This repo provides a starting point and example for creating your own custom [dev container Features](https://containers.dev/implementors/features/), hosted for free on GitHub Container Registry. The example in this repository follows the [dev container Feature distribution specification](https://containers.dev/implementors/features-distribution/).
4
-
>
5
-
> To provide feedback to the specification, please leave a comment [on spec issue #70](https://github.com/devcontainers/spec/issues/70). For more broad feedback regarding dev container Features, please see [spec issue #61](https://github.com/devcontainers/spec/issues/61).
3
+
This repository contains a _collection_ of dev container features
6
4
7
-
## Example Contents
5
+
## Features
8
6
9
-
This repository contains a _collection_ of two Features - `hello` and `color`. These Features serve as simple feature implementations. Each sub-section below shows a sample `devcontainer.json` alongside example usage of the Feature.
7
+
Each sub-section below shows a sample `devcontainer.json` alongside example usage of the Feature.
10
8
11
-
### `hello`
9
+
### `codeql`
12
10
13
-
Running `hello` inside the built container will print the greeting provided to it via its `greeting` option.
11
+
Running `codeql` inside the built container will install the CodeQL CLI and CodeQL language packs bundle.
Similar to the [`devcontainers/features`](https://github.com/devcontainers/features) repo, this repository has a `src` folder. Each Feature has its own sub-folder, containing at least a `devcontainer-feature.json` and an entrypoint script `install.sh`.
23
+
This repository has a `src` folder. Each Feature has its own sub-folder, containing at least a `devcontainer-feature.json` and an entrypoint script `install.sh`.
56
24
57
25
```
58
26
├── src
59
-
│ ├── hello
60
-
│ │ ├── devcontainer-feature.json
61
-
│ │ └── install.sh
62
-
│ ├── color
27
+
│ ├── codeql
63
28
│ │ ├── devcontainer-feature.json
64
29
│ │ └── install.sh
65
30
| ├── ...
@@ -74,36 +39,9 @@ An [implementing tool](https://containers.dev/supporting#tools) will composite [
74
39
75
40
All available options for a Feature should be declared in the `devcontainer-feature.json`. The syntax for the `options` property can be found in the [devcontainer Feature json properties reference](https://containers.dev/implementors/features/#devcontainer-feature-json-properties).
76
41
77
-
For example, the `color` feature provides an enum of three possible options (`red`, `gold`, `green`). If no option is provided in a user's `devcontainer.json`, the value is set to "red".
78
-
79
-
```jsonc
80
-
{
81
-
// ...
82
-
"options": {
83
-
"favorite": {
84
-
"type":"string",
85
-
"enum": [
86
-
"red",
87
-
"gold",
88
-
"green"
89
-
],
90
-
"default":"red",
91
-
"description":"Choose your favorite color."
92
-
}
93
-
}
94
-
}
95
-
```
96
42
97
43
Options are exported as Feature-scoped environment variables. The option name is captialized and sanitized according to [option resolution](https://containers.dev/implementors/features/#option-resolution).
98
44
99
-
```bash
100
-
#!/bin/bash
101
-
102
-
echo"Activating feature 'color'"
103
-
echo"The provided favorite color is: ${FAVORITE}"
104
-
105
-
...
106
-
```
107
45
108
46
## Distributing Features
109
47
@@ -113,76 +51,16 @@ Features are individually versioned by the `version` attribute in a Feature's `d
113
51
114
52
### Publishing
115
53
116
-
> NOTE: The Distribution spec can be [found here](https://containers.dev/implementors/features-distribution/).
117
-
>
118
-
> While any registry [implementing the OCI Distribution spec](https://github.com/opencontainers/distribution-spec) can be used, this template will leverage GHCR (GitHub Container Registry) as the backing registry.
119
-
120
-
Features are meant to be easily sharable units of dev container configuration and installation code.
121
-
122
54
This repo contains a **GitHub Action**[workflow](.github/workflows/release.yaml) that will publish each Feature to GHCR.
123
55
124
56
*Allow GitHub Actions to create and approve pull requests* should be enabled in the repository's `Settings > Actions > General > Workflow permissions` for auto generation of `src/<feature>/README.md` per Feature (which merges any existing `src/<feature>/NOTES.md`).
125
57
126
-
By default, each Feature will be prefixed with the `<owner/<repo>` namespace. For example, the two Features in this repository can be referenced in a `devcontainer.json` with:
127
-
128
-
```
129
-
ghcr.io/devcontainers/feature-starter/color:1
130
-
ghcr.io/devcontainers/feature-starter/hello:1
131
-
```
132
-
133
-
The provided GitHub Action will also publish a third "metadata" package with just the namespace, eg: `ghcr.io/devcontainers/feature-starter`. This contains information useful for tools aiding in Feature discovery.
58
+
By default, each Feature will be prefixed with the `<owner/<repo>` namespace.
134
59
135
-
'`devcontainers/feature-starter`' is known as the feature collection namespace.
60
+
The provided GitHub Action will also publish a third "metadata" package with just the namespace, eg: `ghcr.io/Perdiga/devcontainer-features`. This contains information useful for tools aiding in Feature discovery.
136
61
137
-
### Marking Feature Public
138
-
139
-
Note that by default, GHCR packages are marked as `private`. To stay within the free tier, Features need to be marked as `public`.
140
-
141
-
This can be done by navigating to the Feature's "package settings" page in GHCR, and setting the visibility to 'public`. The URL may look something like:
'`Perdiga/devcontainer-features`' is known as the feature collection namespace.
148
63
149
64
### Adding Features to the Index
150
65
151
-
If you'd like your Features to appear in our [public index](https://containers.dev/features) so that other community members can find them, you can do the following:
152
-
153
-
* Go to [github.com/devcontainers/devcontainers.github.io](https://github.com/devcontainers/devcontainers.github.io)
154
-
* This is the GitHub repo backing the [containers.dev](https://containers.dev/) spec site
155
-
* Open a PR to modify the [collection-index.yml](https://github.com/devcontainers/devcontainers.github.io/blob/gh-pages/_data/collection-index.yml) file
156
-
157
-
This index is from where [supporting tools](https://containers.dev/supporting) like [VS Code Dev Containers](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers) and [GitHub Codespaces](https://github.com/features/codespaces) surface Features for their dev container creation UI.
158
-
159
-
#### Using private Features in Codespaces
160
-
161
-
For any Features hosted in GHCR that are kept private, the `GITHUB_TOKEN` access token in your environment will need to have `package:read` and `contents:read` for the associated repository.
162
-
163
-
Many implementing tools use a broadly scoped access token and will work automatically. GitHub Codespaces uses repo-scoped tokens, and therefore you'll need to add the permissions in `devcontainer.json`
164
-
165
-
An example `devcontainer.json` can be found below.
This repo is listed on dev container [public index](https://containers.dev/features) so that other community members can find them. If you need to update it, open a PR to modify the [collection-index.yml](https://github.com/devcontainers/devcontainers.github.io/blob/gh-pages/_data/collection-index.yml) file
0 commit comments