I don't trust VSCode "devcontainers" to properly contain an LLM working on a codebase. I would really like to use LXD containers as devcontainers instead of regular Docker containers.
Workshop seems like the right tool to do this with, but it doesn't actually integrate with devcontainers.
Currently, I might be able to "hack" it by simply starting an environment and using the "Remote - SSH" extension to connect to it. But that requires a lot of manual work, and I still need to manually install the project-specific tools if there's no SDK config for this project.
I see two possible approaches:
- Create a devcontainer-like feature that uses the workshop config file instead of a devcontainer config file. This feature is part of a vscode extension and hooks into the Remote feature to the remote into the workshop environment. The downside is that the user needs to recreate the devcontainer setup scripts to configure a workshop environment instead.
- Create an integration between devcontainers and workshop that runs the devcontainer inside of the workshop environment. This would be the most seamless experience, but might be a bit more complicated/convoluted.
What do you think?
I don't trust VSCode "devcontainers" to properly contain an LLM working on a codebase. I would really like to use LXD containers as devcontainers instead of regular Docker containers.
Workshop seems like the right tool to do this with, but it doesn't actually integrate with devcontainers.
Currently, I might be able to "hack" it by simply starting an environment and using the "Remote - SSH" extension to connect to it. But that requires a lot of manual work, and I still need to manually install the project-specific tools if there's no SDK config for this project.
I see two possible approaches:
What do you think?