Devcontainer Support Daytonaio Daytona Deepwiki

Loading... Loading... Menu This document provides comprehensive guidance for setting up a local development environment for contributing to the Daytona codebase. It covers the DevContainer-based setup (recommended), manual setup steps, required tools, local services, and initial configuration. For information about the code contribution workflow itself, see Code Contribution Workflow. For project structure and coding conventions, see Project Structure and Conventions. Before setting up your development environment, ensure your system meets the following requirements: Sources: .devcontainer/devcontainer.json52-56 The Daytona repository includes a fully-configured DevContainer that provides all required tools and dependencies.

Sources: .devcontainer/devcontainer.json1-96 .devcontainer/Dockerfile1-29 The DevContainer is defined in .devcontainer/devcontainer.json1-96 and includes: Base Service Configuration: - Service name: app .devcontainer/devcontainer.json4 - Workspace folder: /workspaces/daytona .devcontainer/devcontainer.json5 - Remote user: daytona (UID 1000, GID 1000) .devcontainer/devcontainer.json46-50 Environment Variables: COREPACK_ENABLE_DOWNLOAD_PROMPT=0 - Disable Corepack prompts .devcontainer/devcontainer.json8NX_DAEMON=true - Enable Nx daemon for faster builds .devcontainer/devcontainer.json11NODE_ENV=development .devcontainer/devcontainer.json12POETRY_VIRTUALENVS_IN_PROJECT=true - Python venv in.venv .devcontainer/devcontainer.json13RUBYLIB - Ruby library paths for SDK and API clients .devcontainer/devcontainer.json14 VS Code Extensions Installed: dbaeumer.vscode-eslint - JavaScript/TypeScript lintingesbenp.prettier-vscode - Code formattingnrwl.angular-console - Nx workspace managementms-python.python - Python language supportshopify.ruby-lsp - Ruby language server- Additional extensions for shell, documentation, and UI frameworks Sources: .devcontainer/devcontainer.json7-42 The DevContainer executes commands at different lifecycle stages: onCreateCommand .devcontainer/devcontainer.json79-82: - Creates .env.local file if it doesn't exist - Sets Git safe directory postStartCommand .devcontainer/devcontainer.json83: yarn - Install Node.js dependenciespoetry lock && poetry install - Install Python dependenciesbundle install - Install Ruby gemsdocker buildx create --name builder --driver-opt network=host --config .devcontainer/buildkitd.toml --driver docker-container --use - Configure multi-platform Docker builds Sources: .devcontainer/devcontainer.json79-84 The following ports are automatically forwarded for accessing local services: Sources: .devcontainer/devcontainer.json85-93 - Clone the repository: - Open in VS Code: - Open the repository folder in VS Code - VS Code will detect the DevContainer configuration - Click "Reopen in Container" when prompted - Alternatively, use Command Palette: Dev Containers: Reopen in Container - Wait for initialization: - Initial build may take 10-15 minutes depending on network speed - The postStartCommand will run automatically, installing all dependencies - Verify the setup: Sources: .devcontainer/devcontainer.json57-67 CONTRIBUTING.md61-69 If you cannot use DevContainers, follow these steps to set up your environment manually.

Install the following language runtimes with the specified versions: Go 1.25.4: Node.js 22.14.0: Ruby 3.4.5: Python 3.x with Poetry 2.1.3: Sources: .devcontainer/devcontainer.json57-77 Install these additional tools: golangci-lint 2.6.2: Go Tools: Docker and Docker Compose: - Docker 28.4.0 or later - Docker Compose v2 Sources: .devcontainer/devcontainer.json59 .devcontainer/devcontainer.json72-76 CONTRIBUTING.md69 After installing runtimes and tools, install project dependencies: Sources: .devcontainer/devcontainer.json83 Create a .env.local file in the repository root for local configuration overrides: Set the following environment variables in your shell: Sources: .devcontainer/devcontainer.json10-15 .devcontainer/devcontainer.json81 The Daytona development environment requires several backing services that run via Docker Compose.

Sources: .devcontainer/docker-compose.yaml (referenced but not provided), .devcontainer/devcontainer.json85-93 The Docker Compose services are automatically started when using the DevContainer. For manual setup: Sources: .devcontainer/devcontainer.json3 Daytona uses Nx to manage the monorepo and orchestrate builds across multiple languages.

Nx Features Used: - Computation caching in .nx/cache .gitignore43 - Workspace data in .nx/workspace-data .gitignore44 - Daemon mode for faster builds: NX_DAEMON=true .devcontainer/devcontainer.json11 Build Artifacts (Ignored in Git): dist/ - Compiled output .gitignore4node_modules/ - Node.js dependencies .gitignore9.venv/ - Python virtual environments .gitignore78vendor/bundle/ - Ruby gems .gitignore72.nx/cache/ - Nx computation cache .gitignore43 Sources: .gitignore1-86 .devcontainer/devcontainer.json11 Several scripts automate code generation when making changes to the API or CLI: When modifying the OpenAPI specification, regenerate API clients: This script: - Reads the OpenAPI specification - Generates API client libraries for Python, TypeScript, Go, and Ruby - Updates SDK dependencies Sources: CONTRIBUTING.md67 When adding or modifying CLI commands, regenerate documentation: This script: - Parses CLI command definitions - Generates markdown documentation - Updates the CLI reference pages Sources: CONTRIBUTING.md66 The project uses golangci-lint for Go code quality checks: All Go code must pass linting before a pull request can be merged.

CONTRIBUTING.md69 For Node.js projects: Sources: CONTRIBUTING.md69 .devcontainer/devcontainer.json21 The project uses different package managers for each language: Important: Always use yarn , not npm . CONTRIBUTING.md68 Virtual environments are created in .venv directories within each project. .devcontainer/devcontainer.json13 The Gemfile.lock at the root is tracked in Git. .gitignore74 Sources: CONTRIBUTING.md68 .devcontainer/devcontainer.json13-15 .gitignore74 For contributors working on Docker images, the repository includes Buildx configuration: The DevContainer creates a Buildx builder instance: This enables building images for both amd64 and arm64 architectures.

.devcontainer/devcontainer.json83 The Buildkit daemon configuration is stored in .devcontainer/buildkitd.toml (not provided but referenced) and customizes caching and networking behavior. Sources: .devcontainer/devcontainer.json83 After completing the setup, verify that everything works correctly: Sources: .devcontainer/devcontainer.json57-77 CONTRIBUTING.md69 Solution: Ensure Go is in your PATH: For DevContainer users, this should be automatic. .devcontainer/devcontainer.json57-59 Solution: Ensure Docker is running and you have permissions: The DevContainer includes Docker-in-Docker support. .devcontainer/devcontainer.json52-56 Solution: Install golangci-lint: Sources: CONTRIBUTING.md69 Solution: Enable Corepack: Sources: .devcontainer/devcontainer.json8 Solution: Clear Nx cache: Sources: .gitignore43-44 Solution: Check forwarded ports and adjust if necessary.

The DevContainer forwards these ports by default: 5556, 80 (pgadmin), 5100 (registry-ui), 1080 (maildev), 9000-9001 (minio), 16686 (jaeger). Stop conflicting services or modify .devcontainer/devcontainer.json85-93 Sources: .devcontainer/devcontainer.json85-93 After completing the development environment setup: - Review the contribution workflow: See Code Contribution Workflow for information about forking, committing with DCO sign-off, and creating pull requests. - Understand project structure: See Project Structure and Conventions for monorepo layout, naming conventions, and coding standards. - Learn the build process: See Release and Build Process for CI/CD pipeline details.

Refresh this wiki - Development Environment Setup - Prerequisites - DevContainer Setup (Recommended) - DevContainer Architecture - DevContainer Configuration Details - Lifecycle Commands - Port Forwarding - Starting the DevContainer - Manual Setup (Alternative) - Required Language Runtimes - Required Development Tools - Dependency Installation - Environment Variables - Local Development Services - Services Architecture - Starting Local Services - Build System and Monorepo Structure - Nx Workspace Configuration - Code Generation Tools - API Client Generation - CLI Documentation Generation - Linting and Code Quality - Running the Linter - ESLint for TypeScript/JavaScript - Package Management - Node.js: Yarn via Corepack - Python: Poetry - Ruby: Bundler - Go: Go Modules - Docker Build Configuration - Multi-Platform Builds - BuildKit Configuration - Verification and Testing - Environment Verification Checklist - Commands to Run - Common Issues and Troubleshooting - Issue: "go: command not found" - Issue: "Cannot connect to Docker daemon" - Issue: "golangci-lint: command not found" - Issue: "yarn: command not found" - Issue: Build cache taking too much space - Issue: Port conflicts with local services - Next Steps

People Also Asked

• Devcontainer Support | daytonaio/daytona | DeepWiki
• GitHub - daytonaio/daytona: Daytona is a Secure and Elastic ...
• Documentation · Daytona
• Development Environment Setup | daytonaio/daytona | DeepWiki
• The base devcontainer for Daytona Go projects - GitHub
• Daytona: Your Project's New Best Friend - DEV Community
• Getting Started with Daytona: A Beginner's Guide to Development ...