bazelbuild / bazelbuild/bazel

All builds inside docker dev containers?

Open
#25,108 1 comment 0 reactions 0 assignees View on GitHub
team-Core type: feature request untriaged
Dominant language
Java
Stars
25.8k
Forks
4.6k
Avg merge
2d 20h
Merged PRs (30d)
72

Description

### Description of the feature request:

I was just learning about [dev containers](https://code.visualstudio.com/docs/devcontainers/containers) and wondered whether it would be possible for Bazel to just use containers to perform builds for each package?

So the build would just run off of the `.devcontainers` meta data resources, and produce output outside of the container.

I think Bazel would just need to extend the [devcontainer.json](https://code.visualstudio.com/docs/devcontainers/containers#_create-a-devcontainerjson-file
) file with some additional Bazel required meta data, and then we're off to the races.

This way the build is "Hermetic" and simple. It essentially eliminates the Bazel learning curve and provides developers with a development environment at the same time.

### Which category does this issue belong to?

Core

### What underlying problem are you trying to solve with this feature?

Learning curve for Bazel is steep.

### Which operating system are you running Bazel on?

MacOS

### What is the output of `bazel info release`?

_No response_

### If `bazel info release` returns `development version` or `(@non-git)`, tell us how you built Bazel.

_No response_

### What's the output of `git remote get-url origin; git rev-parse HEAD` ?

```text

```

### Have you found anything relevant by searching the web?

_No response_

### Any other information, logs, or outputs that you want to share?

_No response_

Contributor guide

Open the contributing guide

Research direction

The request names devcontainer.json and Bazel but no repository files or tests. Start by reviewing the dev container metadata and Bazel's build execution and hermeticity entry points; define the required metadata, container boundaries, output handling, and a complete build workflow before implementation.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker
Domain
build-system, devops
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.