Skip to content

cdsolinfo/devcontainer-features

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

4 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Dev Container Features: cdsolinfo/devcontainers

This repository hosts custom dev container Features, published to GitHub Container Registry (GHCR) following the dev container Feature distribution specification.

Features

ksm — Keeper Secrets Manager

Installs the Keeper Secrets Manager CLI (ksm) and forwards KSM_CONFIG from the local host environment into the container.

KSM_CONFIG holds the base64-encoded configuration used to authenticate with Keeper Secrets Manager. This feature uses the devcontainer containerEnv mechanism (${localEnv:KSM_CONFIG}) to transparently pass the variable from your local machine into the container, so the KSM CLI is ready to use without any manual setup inside the container.

Security note: KSM_CONFIG contains sensitive credentials. Ensure your container is properly isolated and that the value is not logged or exposed via container introspection (e.g., docker inspect). Avoid committing KSM_CONFIG to source control or sharing it in logs.

{
    "image": "mcr.microsoft.com/devcontainers/base:ubuntu",
    "features": {
        "ghcr.io/cdsolinfo/devcontainers/ksm:1": {}
    }
}

Options

Option Id Description Type Default
version Select the version of KSM CLI to install. Use latest for the most recent version. string latest

Repo and Feature Structure

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.

├── src
│   ├── ksm
│   │   ├── devcontainer-feature.json
│   │   ├── install.sh
│   │   └── README.md
...

An implementing tool will composite the documented dev container properties from the feature's devcontainer-feature.json file, and execute the install.sh entrypoint script in the container during build time.

Distributing Features

Versioning

Features are individually versioned by the version attribute in a Feature's devcontainer-feature.json. Features are versioned according to the semver specification. More details can be found in the dev container Feature specification.

Publishing

NOTE: The Distribution spec can be found here.

While any registry implementing the OCI Distribution spec can be used, this template will leverage GHCR (GitHub Container Registry) as the backing registry.

Features are meant to be easily sharable units of dev container configuration and installation code.

This repo contains a GitHub Action workflow that will publish each Feature to GHCR.

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).

By default, each Feature will be prefixed with the <owner>/<repo> namespace. For example, the Feature in this repository can be referenced in a devcontainer.json with:

ghcr.io/cdsolinfo/devcontainers/ksm:1

The provided GitHub Action will also publish a third "metadata" package with just the namespace, eg: ghcr.io/cdsolinfo/devcontainers. This contains information useful for tools aiding in Feature discovery.

'cdsolinfo/devcontainers' is known as the feature collection namespace.

Marking Feature Public

Note that by default, GHCR packages are marked as private. To stay within the free tier, Features need to be marked as public.

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:

https://github.com/users/cdsolinfo/packages/container/devcontainers%2Fksm/settings

image

Adding Features to the Index

If you'd like your Features to appear in our public index so that other community members can find them, you can do the following:

This index is from where supporting tools like VS Code Dev Containers and GitHub Codespaces surface Features for their dev container creation UI.

Using private Features in Codespaces

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.

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

An example devcontainer.json can be found below.

{
    "image": "mcr.microsoft.com/devcontainers/base:ubuntu",
    "features": {
     "ghcr.io/my-org/private-features/hello:1": {
            "greeting": "Hello"
        }
    },
    "customizations": {
        "codespaces": {
            "repositories": {
                "my-org/private-features": {
                    "permissions": {
                        "packages": "read",
                        "contents": "read"
                    }
                }
            }
        }
    }
}

About

No description, website, or topics provided.

Resources

License

Stars

Watchers

Forks

Packages

 
 
 

Contributors

Languages