---------------------- To ensure that the Garden console displays output from the command you execute in the container, you can set the log-level to

verbose

or higher. This can be done by using the

--log-level

flag followed by

verbose

when running your command. Here is an example:

bash
garden build --log-level verbose

This command will set the log-level to verbose, which should allow you to view the output of the executed command in the Garden console. If you're still having trouble viewing the logs, it might be due to a known issue where

garden exec

suppresses logs when run within a workflow. You can follow the progress of this issue on the Garden GitHub page (). Sources: - How do I view container build logs? () - Github Issue: Bug: Garden exec within a workflow suppresses logs () ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ----------------------

message has been deleted

---------------------- To set a global option like log level in the Garden console, you can use the

--log-level

flag followed by the desired log level. The log level can be set to

error

,

warn

,

info

,

verbose

,

debug

,

silly

, or a numeric value from

0

to

5

. Here is an example of how to set the log level to `debug`:

bash
garden build --log-level debug

This command will set the log level to

debug

, which is one of the most detailed levels of logging. You can also use the

-l

alias for the

--log-level

flag. Here is the same command using the

-l

alias:

bash
garden build -l debug

Remember that all option flags can be specified with a space or a

=

between the flag and the value. Source: Global options () ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ----------------------

message has been deleted