Many opensource projects use devcontainers to define how to quickly install the prerequisites for building/developing on that project. It is cumbersome to manually specify a new template for every project I want to work on within coder, so I am happy to see that the devcontainer module supports automatically pulling and setting up the container within which I can work to hack on different projects.

However, I tried to install other modules such as tmux, mux, vscode-web, etc... and I have found that these modules do not execute within the context of the devcontainer, they are instead within the context of the main container. This seems like a big downside, as my coding agents now do not have the ability to build or run tests on the codebase under development.

I'm not a terraform or coder expert, so I hesitate to suggest the right approach to solve this problem. I'm also willing to accept workarounds if any can be presented, but I feel that proper composability for the modules used in templates would be very helpful. Specifying that a module should be executed within a container generated by another module, for instance, would be the natural way I would think about this, and provide a very flexible mechanism for complicated projects that contain many nested containers (but would allow for container-specific terminal/vscode-web instances for debugging, etc..)

I believe this is related to #21134 and perhaps #15143