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

"ddev logs" should work against stopped containers #719

Closed
rfay opened this issue Mar 9, 2018 · 1 comment
Closed

"ddev logs" should work against stopped containers #719

rfay opened this issue Mar 9, 2018 · 1 comment

Comments

@rfay
Copy link
Member

rfay commented Mar 9, 2018

What happened (or feature request):

Now that we have changed containers not to restart, we need to make ddev logs work against stopped containers. Docker is fine with this, and it's actually quite a lot better for us, but currently ddev refuses to do it and you have to docker ps -a and use docker logs to find out the reason for a failure.

What you expected to happen:

How to reproduce this:

Version: Please include the output of ddev version, docker version and the project's .ddev/config.yaml.

Anything else do we need to know:

Related source links or issues:

Please use a complexity rating of 1-5 (5 is high) for a feature request. (High complexity implies more PR planning)

@rickmanelius
Copy link
Contributor

Related #642 (so that projects can be targetted from anywhere). Otherwise, you would have to be in the working directory anyway.

Good idea. Not sure it's urgent, but certainly a good wishlist item!

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

No branches or pull requests

2 participants