All builds inside docker dev containers?

[fireflysemantics]

Description of the feature request:

I was just learning about dev 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 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 ?

Have you found anything relevant by searching the web?

No response

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

No response