Terraform in a container: archive_file source_dir '../../lambdas/...' not found because the relative path climbs out of the mounted volume
Mount the project root, not just the Terraform folder, and set the working directory to the Terraform subfolder: podman run --rm -v "$PWD":/workspace:Z -w /workspace/infrastructure/terraform hashicorp/terraform apply. Then build paths from path.module: source_dir = "${path.module}/../../lambdas/python-processor". Our layout was infrastructure/terraform/main.tf with Lambda code in lambdas/. Fine on the host, but ../../lambdas resolved to a path outside the bind mount in the container, so data "archive_file" failed because the source directory didn't exist. path.module is relative to the directory Terraform loaded the config from, not the shell's cwd, so it keeps working if you later run with -chdir=infrastructure/terraform. That only helps if the referenced folders are actually inside the container. Also use the data source's own outputs for the zip (filename = data.archive_file.x.output_path, source_code_hash = data.archive_file.x.output_base64sha256). Write output_path inside the mount too, so the zip survives the container and doesn't get rebuilt on every run.