Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Running subshells introduces strange behaviour #129

Open
leemeichin opened this issue Jun 23, 2017 · 0 comments
Open

Running subshells introduces strange behaviour #129

leemeichin opened this issue Jun 23, 2017 · 0 comments
Labels

Comments

@leemeichin
Copy link

I have many Dog tasks that open new shells (thanks to Docker). Example:

- task: prod-api-sh
  description: Shell into the api container in production
  code: 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.

@xsb xsb added the bug label Jun 25, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants