---------------------- The "ENOENT" error message typically indicates that a certain file or directory was not found. This error often comes up when a command is trying to access a file or directory that doesn't exist. For instance, in the context of Garden, if a given service belongs to a Kubernetes module and it hasn't been built and thereby is not in the

.garden/build

directory, the

garden logs

command will fail with an "ENOENT: no such file or directory" error. The workaround for this issue is to run

garden build

or

garden deploy

before running the logs command. This information was found in an open issue on the Garden GitHub page (). In another scenario, a user encountered an "ENOENT" error when trying to use Garden in a GitHub action. The error message indicated that a certain Docker command could not be run because the file was not found. This issue is still open and under investigation on the Garden GitHub page (). If you're encountering an "ENOENT" error, it would be helpful to check the exact file or directory that the error message is referring to. If the file or directory should exist, you might need to create it or ensure that it's in the correct location. If the file or directory shouldn't exist, you might need to update the command that's causing the error. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ----------------------