Help! Why is there no configuration information on the worker container build.log file

[scottmorgan-payroc]

The build.log grows out of control taking over all of the worker container disk space. How does one throttle or configure max size/rollover of the workers build.log file?

[scottmorgan-payroc]

The only relief I could get to the endless disk space consumption was to run

1. docker exec airbyte-worker rm build.log
2. docker exec airbyte-worker touch build.log

After running above the size stays at zero bytes

[pedrohsroque]

Same issue here,
we reached 60GB this week...

[scottmorgan-payroc]

With abctl local install I haven’t run into the build.log bloat yet. My solution under docker compose was to create. Job that deleted the build.log file then used a touch command to create an empty build. log file. After creating an empty build.log file the file never grew again Get Outlook for iOS<https://aka.ms/o0ukef> Scott Morgan Senior Director, Data Engineering e: ***@***.*** w: www.payroc.com

…

________________________________ From: Pedro Roque ***@***.***> Sent: Friday, November 1, 2024 2:00:25 PM To: airbytehq/airbyte ***@***.***> Cc: Scott Morgan ***@***.***>; Author ***@***.***> Subject: Re: [airbytehq/airbyte] Help! Why is there no configuration information on the worker container build.log file (Discussion #36506) Same issue here, we reached 60GB this week... — Reply to this email directly, view it on GitHub<#36506 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ATU2AEPS4Y66XUVN3SDMX53Z6O6TTAVCNFSM6AAAAABRAWOSYWVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCMJSGQ3TQNA>. You are receiving this because you authored the thread.Message ID: ***@***.***>