atmos-devcontainer
Atmos Devcontainer
Purpose
Atmos provides native devcontainer management for creating standardized, reproducible development environments. It provides built-in orchestration that integrates with Atmos authentication, toolchains, and project configuration, replacing the need for external orchestration tooling like Geodesic (though Geodesic container images remain fully supported).
Note: The devcontainer feature is currently experimental. By default (settings.experimental: warn),
Atmos displays a warning but runs the command. Set settings.experimental: silence in atmos.yaml to
suppress the warning, or disable to block experimental commands entirely.
Core Concepts
Devcontainer Configuration
Devcontainers are configured at the top level of atmos.yaml (not under components:).
Each named devcontainer defines container settings and a devcontainer spec:
More from cloudposse/atmos
atmos-design-patterns
Design patterns: stack organization, component catalogs, inheritance, configuration composition, version management, layered configuration
15atmos-config
Project configuration: atmos.yaml structure, all sections, discovery, merging, base paths, settings, imports, profiles
12atmos-workflows
Workflow automation: multi-step workflows, Go template support, cross-component orchestration
12atmos-helmfile
Helmfile orchestration: sync/apply/destroy/diff, Kubernetes deployments, varfile generation, EKS integration, source management
12atmos-stores
Store backends: AWS SSM, Azure Key Vault, Google Secret Manager, Redis, Artifactory configuration, hooks integration, cross-component data sharing
11atmos-stacks
Stack configuration: imports, inheritance, deep merging, locals, vars, settings, metadata, overrides
10