---------------------- The reason

exec <pod> -i -- sh

does not work as expected in the Garden dev console is that the

exec

command is not supported inside the interactive dev console. According to the official documentation, to shell into a running Pod using Garden's

exec

utility, you must run the command from a separate terminal window, not from within the dev console. The documentation explicitly states: > One other way to test syncing is by shelling into the running Pod and verifying that the files have updated with the Garden

exec

utility command. To e.g. shell into the API, run the following from a separate terminal window (exec doesn't work inside the dev console):

garden exec api /bin/sh

This means that while

garden exec <pod> -i -- sh

works from your terminal, it is not designed to work from within the dev console, which is why you only see "Command exec completed successfully!" without an interactive shell session starting [Step 4 — Verify that code syncing works](). ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ----------------------

message has been deleted