You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have many Dog tasks that open new shells (thanks to Docker). Example:
- task: prod-api-shdescription: Shell into the api container in productioncode: convox exec $(convox ps | grep api | cut -f1 -d' ') sh
The code is pretty much the same as running docker exec -it api_container sh.
This works fine, but the resulting shell behaves strangely. Random control codes are inserted straight after the prompt, and signals go straight to Dog rather than the subshell. This means that hitting Ctrl+C to terminate a command inside the container actually terminates the container itself. Arrow keys don't work, neither do the usual movement shortcuts (Ctrl+A, Ctrl+E), and colours don't work either.
The text was updated successfully, but these errors were encountered:
I have many Dog tasks that open new shells (thanks to Docker). Example:
The code is pretty much the same as running
docker exec -it api_container sh
.This works fine, but the resulting shell behaves strangely. Random control codes are inserted straight after the prompt, and signals go straight to Dog rather than the subshell. This means that hitting Ctrl+C to terminate a command inside the container actually terminates the container itself. Arrow keys don't work, neither do the usual movement shortcuts (Ctrl+A, Ctrl+E), and colours don't work either.
The text was updated successfully, but these errors were encountered: