A Terraform provider for managing Docker containers, images, networks, and volumes as infrastructure-as-code.
The Terraform Docker Provider is a Terraform plugin that enables infrastructure-as-code management of Docker resources. It allows users to define Docker containers, images, networks, and volumes using Terraform's declarative configuration language, making Docker infrastructure reproducible and version-controlled.
DevOps engineers, infrastructure developers, and teams using Docker who want to manage containerized infrastructure as code with Terraform.
It provides a declarative, version-controlled approach to Docker management, integrating seamlessly with Terraform's ecosystem for consistent infrastructure provisioning and state management across environments.
As part of our introduction to self-service publishing in the Terraform Registry, this copy of the provider has been archived, and ownership has been transferred to active maintainers in the community. Please see the new location on the Terraform Registry: https://registry.terraform.io/providers/kreuzwerker/docker/latest
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Uses Terraform's HCL to define Docker resources as code, enabling version-controlled and reproducible configurations as per the project's philosophy.
Seamlessly integrates with other Terraform providers, allowing unified management of Docker alongside cloud or on-prem infrastructure.
Maintains state of Docker resources across deployments, facilitating consistency and automatic detection of configuration changes.
Now actively maintained by kreuzwerker on the Terraform Registry, ensuring ongoing updates and community-driven improvements as noted in the README.
Requires Terraform expertise and additional configuration, with building from source needing Go 1.15.x and make commands, adding overhead for simple Docker tasks.
As a community-maintained provider, it may lag behind native Docker tools in supporting new features or edge cases, with potential risks during the transition from HashiCorp.
The README notes that continuous integration for Windows is unavailable due to lack of free CI providers, hindering testing and development on Windows platforms.