I have a `kubernetes-exec` run that is running a p...
# 🤖|ask-kapa
f
@microscopic-river-74022 I have a
kubernetes-exec
run that is running a pytest process in a running container. It displays output when I run it locally, but it does not display the output in the garden console. How can I ensure that the garden console displays output from the command I execute in the container?
m
Please stand by @fresh-yak-35965 as I search the knowledge base. I normally take about 20 seconds or so. :wave:
---------------------- 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:
Copy code
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
f
@microscopic-river-74022 How do I set a global option like log level in the garden console?
m
Let me check the knowledge base for you. One moment! :books:
---------------------- 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`:
Copy code
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:
Copy code
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