You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The large file "../fcos.vhd" should be present in the destination container
Actual Behaviour
Terraform apply results in OOM stack trace. The "../fcos.vhd" is a Fedora Core OS image and ~10Gbyte in size, the machine has ~7Gbyte of free memory. It seems that the resource provider tries to pull the file into memory before upload and rightfully crashes trying to do so.
If this is a by-design limitation then it would be nice to receive a hint (eg. "The current amount of memory might not be large enough to sucessfully execute the operation") during "terraform plan".
Steps to Reproduce
No response
Important Factoids
none
References
No response
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Community Note
Terraform Version
1.4.5
AzureRM Provider Version
3.51.0
Affected Resource(s)/Data Source(s)
azurerm_storage_blob
Terraform Configuration Files
Debug Output/Panic Output
Expected Behaviour
The large file "../fcos.vhd" should be present in the destination container
Actual Behaviour
Terraform apply results in OOM stack trace. The "../fcos.vhd" is a Fedora Core OS image and ~10Gbyte in size, the machine has ~7Gbyte of free memory. It seems that the resource provider tries to pull the file into memory before upload and rightfully crashes trying to do so.
If this is a by-design limitation then it would be nice to receive a hint (eg. "The current amount of memory might not be large enough to sucessfully execute the operation") during "terraform plan".
Steps to Reproduce
No response
Important Factoids
none
References
No response
The text was updated successfully, but these errors were encountered: