There are a few:
- Shorter commands removing redundant steps (.
/launcher enter appis just./launcher exec app bashexcept you’re stuck in bash without the defaults that you’re accustomed to, and then you still need to run the command you actually wanted to run (ie,discourse restore. Also, inside the container’s bash you constantly (every rebuilt) loose all your shell history and the history settings inside the container are probably not what you’re used to. You’re also forced to use bash instead of zsh or whatever shell you might normally use. - How do you automate anything on the host that operates on your container without this? For example, the script I outlined above that we run on our staging site each night… grabs our database from live and restores it onto dev. I imagine you don’t want to write expect scripts to automate a terminal session…