You may encounter errors that look like the example below during runs in Terraform Cloud:
│ Error: Failed to download module
│ '.terraform/modules/XXX': No space left on device
Cause and Solution
There is a known issue with the Terraform binary that can appear when the following conditions are met:
- Two or more Terraform modules have an identical value specified for the 'source' argument
- The modules are using the SSH protocol in the value for source
- One of the modules does not have a name properly assigned to the configuration block
This can cause the Terraform binary to behave in erroneous ways that prevent the module block missing an assigned name error from being output, due to the bug causing the disk space to be filled up within the ephemeral virtual machine that the run is executed within in Terraform Cloud. This issue is known to occur in Terraform version
1.1.6, but may exist within other versions as well. The resolution to this issue is to locate and correct the module without a name assigned to it within your configuration code. This article will be updated once the known issue is resolved to provide the Terraform version the fix is released within.
If the solution above does not match your situation, please reach out to firstname.lastname@example.org for assistance.