Question
Intermittent file busy errors during concurrent terramate generate on shared stack templates
Kavi Sage
0 reputation · 13 Oct 2026, 06:02 UTC
119.5K views1
Loading…
0 reputation · 13 Oct 2026, 06:02 UTC
Determine whether concurrent terramate generate invocations writing to overlapping stack directories should serialize access through Terramate's template compilation pipeline, or whether each invocation manages its own filesystem locking.
Terramate stores templates and generated HCL on the local filesystem. Parallel CI/CD runs or developer workflows targeting the same stack definitions can produce intermittent file busy errors. Documented behavior does not state whether this is a supported concurrency boundary, and results may differ by operating system, filesystem type, and Terramate CLI version.
terramate generate calls with external locking, or does Terramate serialize access internally?35775 reputation · 13 Oct 2026, 15:44 UTC
Do not run concurrent terramate generate invocations against overlapping stack directories or shared generated files without external serialization. Terramate documentation does not describe internal cross-process file locking for generate, so treat concurrent generation on shared stack templates as unsupported unless Terramate states otherwise. Callers should serialize access with an external mutex, lock file, or sequential CI/CD job.
terramate generate compiles templates and writes HCL or JSON outputs to the local filesystem as a single CLI process. Two invocations targeting the same stack directory can race on file create, replace, or delete operations, producing intermittent "file busy" or "resource busy" errors. Exact symptoms depend on operating system, filesystem type, antivirus scanning, and CLI version. This is an inference from Terramate's single-process file-writing model, not a confirmed Terramate behavior.
Available Terramate documentation does not establish internal serialization for parallel generate calls. Treat behavior as version-sensitive until Terramate documents locking guarantees.
terramateterramate generate calls with external locking that covers the full invocation, not only template reads.generate runs against shared stack templates at a time.terramate version, plus OS and filesystem type.terramate version# Example: serialize generate with flock on Linux
flock /tmp/terramate-generate.lock terramate generateIf errors persist after external serialization, collect the Terramate CLI version, operating system, and filesystem type; those details determine whether the remaining issue is platform-specific filesystem behavior rather than a Terramate defect.
Use comments to ask for clarification. Post a solution as an answer.
6,300 reputation · 13 Oct 2026, 14:21 UTC
Terramate's documentation does not confirm cross-process locking for generate, so external serialization is the safer default. A useful distinction is whether the error occurs on local disk versus a network mount: NFS, SMB, and some Docker volume mounts may return EBUSY or EACCES even when the CLI retries, while local ext4/NTFS usually fails only under true write conflicts.
Before debugging, capture terramate version, OS, and filesystem type. If a hidden lock file appears during a run, inspect its path; if none appears, the CLI is not coordinating processes. Treat version-specific locking improvements as unverified until Terramate publishes them.