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

Cannot do interactive debugging (without recreating the container) #2386

Closed
CrimsonGlory opened this issue Nov 12, 2015 · 3 comments
Closed

Comments

@CrimsonGlory
Copy link
Contributor

Currently I can do interactive debugging with

docker-compose run --service-ports web

This is as described in issue #359 . But over time I end up with many containers, as run creates a new one each time.
I would like something like:

docker-compose start --bind web

Something to start all the containers, but be able to do interactive debugging of a specific one.
I'm using pry

@dnephin
Copy link

dnephin commented Nov 12, 2015

You can use docker-compose run --service-ports --rm to remove the container once it exits.

@CrimsonGlory
Copy link
Contributor Author

Thanks!

@CrimsonGlory
Copy link
Contributor Author

For those reaching this issue from google (docker compose + interactive debugging).
I'm currently debugging using stdin_open: true in docker-compose.yml and when the program reaches binding.pry or embed() or your favorite debugger, I do docker attach containername and get to the debugger.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants