Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Feature request: devcontainer build --build-output-folder

Open
#1,305 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
55/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
docker, typescript
Domain
build-system, cli

Research direction

Start by locating the devcontainer build command and the preparation flow that generates the Dockerfile and dev container features before invoking Docker. The feature is done when --build-output-folder writes those build inputs to the requested folder and stops before docker build, allowing the output to be used by other build tools.

Written by the indexing model from the issue text.

Description

It would be nice it devcontainer build would have an option --build-output-folder. If such a folder is given, devcontainer uses the devcontainer.json etc. and prepares in the build-output-folder the Dockerfile, the dev container features, etc., but stops before running docker build. One could then use this build output folder, e.g., to lint the resulting Dockerfile using hadolint, start docker build with additional arguments, or use other container building tools like apple/container or kaniko which are no drop-in replacement for docker.

Dominant language
TypeScript
Stars
3k
Forks
461
Avg merge
18m
Merged PRs (30d)
5

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from devcontainers/cli

All issues in devcontainers/cli

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.