Skip to main content

​
crewship features

Lists devcontainer features Crewship can install on a crew’s runtime image, and the curated set of recommended base images. Useful when authoring a devcontainer_config for a crew — you can browse the catalog without leaving the terminal.
Backed by GET /api/v1/features/catalog (24-hour server-side cache). Requires authentication.

​
Subcommands

​
list

Flags: Example:
Columns: NAME, CATEGORY (runtime, tool, language, …), SOURCE (feature publisher, with · <tier> appended when the catalog entry carries a tier), SIZE (rough on-disk impact), REF (the OCI ref to paste into devcontainer_config.features).

​
info

Show full details for a specific feature. Example:
Categories are one of languages, tools, cloud, databases. Size hints are approximate installed deltas. The info view does not surface the feature’s option schema — for that, read the upstream devcontainer-feature.json in the feature’s source repo (the Ref is an OCI reference; the source is usually linked from the same GitHub org).

​
base-images

Lists the curated base images recommended by Crewship for crew runtimes. Same set as crewship runtimes returns for the underlying mise-managed tool versions, but specifically the container base layer. Example:
The full catalog also includes Rust (mcr.microsoft.com/devcontainers/rust:bookworm) and Java 21 (mcr.microsoft.com/devcontainers/java:21-bookworm) entries. The [RECOMMENDED] tag is appended to the label of the curated default(s); there is no separate “default” column. Operators are not restricted to this list — any glibc-based Linux image works. The catalog is what the UI offers in the runtime picker, and the source of truth lives in cmd/crewship/cmd_features.go (baseImagesCatalog).

​
Notes

  • All three subcommands hit the running server (require crewship login). The 24-hour cache means a freshly published feature in the upstream registry can take up to 24h to appear here.
  • Output respects the global --format flag (table, json, yaml).