Receiving message "The lock on the global config store was compromised. Updating the config anyway." garden.io #🌱

Receiving message "The lock on the global config s...

ancient-caravan-7822

04/30/2025, 12:19 PM

I've started getting this message when I deploy a project (it appears to have started this morning with no changes on my end). Just wanted to report it since the message asked me to 🙂 thanks!

Copy code

Warning: The lock on the global config store was compromised. Updating the config anyway.
Warning: The lock on the global config store was compromised. Updating the config anyway.
Warning: The lock on the global config store was compromised. Updating the config anyway.
Warning: Unable to release the lock on the global config store; lock was already released. If you run into this error repeatedly, please report on our GitHub or Discord
Warning: The lock on the global config store was compromised. Updating the config anyway.
Warning: The lock on the global config store was compromised. Updating the config anyway.
Warning: The lock on the global config store was compromised. Updating the config anyway.
Warning: The lock on the global config store was compromised. Updating the config anyway.
Warning: The lock on the global config store was compromised. Updating the config anyway.
Warning: Unable to release the lock on the global config store; lock was already released. If you run into this error repeatedly, please report on our GitHub or Discord
Warning: The lock on the global config store was compromised. Updating the config anyway.
Warning: The lock on the global config store was compromised. Updating the config anyway.
Warning: The lock on the global config store was compromised. Updating the config anyway.
Warning: The lock on the global config store was compromised. Updating the config anyway.
Warning: Unable to release the lock on the global config store; lock was already released. If you run into this error repeatedly, please report on our GitHub or Discord
Warning: Unable to release the lock on the global config store; lock was already released. If you run into this error repeatedly, please report on our GitHub or Discord

ancient-caravan-7822

05/01/2025, 12:28 PM

Does anyone have any advice on dealing with this issue? It's really causing me problems. Things I have tried: - Uninstalled and reinstalled Garden (v 0.13.59) - Deleted the local

.garden

directory and let it get recreated - Restarting the

garden

pod in my k8s namespace - Restarting my machine - Logging in-and-out of Garden Any help would be appreciated - thanks!

ancient-caravan-7822

05/01/2025, 1:11 PM

Problem solved!! It was on my end - I introduced a directory to the project that had lots of subdirectories and files. Garden's scanning of these directories was causing the problem, and adding the file to my

.gardenignore

file solved it. 👍

big-spring-14945

05/21/2025, 12:33 PM

Hi @ancient-caravan-7822 , I am happy you managed to solve the problem on your own, though I am curious what kind of files were in that subdirectory that triggered the issue? We decided to remove the global config lock recently (https://github.com/garden-io/garden/pull/7237). This will be part of the next Garden release and should eliminate this class of problem entirely.

Previous Next