-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Add devcontainer setup for AI coding agents #3437
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
- Dockerfile with Python 3.12, uv, pre-commit, deno - docker-compose with optional services (Ollama, PostgreSQL, pgvector) - docs with setup instructions - platform compatibility (x86_64) to support all dependencies (tested on an M4 chip)
|
@dsfaccini I have been working on a similar dev container here. It is based on the official Python 3 dev container template. I try to keep the container fairly unopinionated and mount I would also suggest to use Ollama from host systems. Inside the container it is much slower. |
|
hey @lars20070 ! thank you for your input. this setup isn't mounting about ollama, I agree with you that running it on the host is the better alternative: this setup doesn't remove that possibility, the commented-out placeholder for ollama is there to offer users an easy way to set up an ollama quickly, if they don't already have one running. I ran _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ |
summary
hey guys, this as a draft PR to add a devcontainer config for AI coding agents (claude code, cursor, et al) and just ol' flesh and bone contributors.
I included an
install.shthat is used to initialize the devcontainer either in standard mode (default) or full ML dev mode (pytorch etc).standard takes a couple of minutes on my machine (m4, 24gb) and full ML dev mode more like 10 min.
I recommend using Orbstack instead of Docker Desktop (seems to be easier on my system's resources) but only if you know how to set it up.
lastly, I'm not an expert in devcontainers so this is largely built by claude itself but I built it on my machine multiple times until it was smooth enough, so I hope that's your experience too. Otherwise let me know!
facts
files
.devcontainer/Dockerfile- container image with all dev tools.devcontainer/devcontainer.json- VS Code configuration and settings.devcontainer/docker-compose.yml- service orchestration.devcontainer/.env.example- API keys template.devcontainer/mcp-proxy-config.json- MCP server integration.devcontainer/README|AGENTS.md- docs and agent guidelinesmore facts
testing
compose, but I haven't tested themreferences
This implementation follows best practices from: