ctop
ctop copied to clipboard
bcicen
pressing key 'e' for exec does nothing
Pressing e for exec is mentioned in the README.md file but it seams it is not implemented.
I encounter the same problem. When I first install ctop, key e only works once and it stops working now.
This doesn't happen to me. However, it seems that I have to press it twice after the first time using it.
Some containers may not have a shell e.g. portainer/portainer-ce. In this case nothing will happen, not even an error shown.
Could you please confirm that you can open shell to the container manually by running:
docker exec -it your_container /bin/sh
If you can't then ctop can't ether. But this may be an UI problem so please check.
This problem is the same for me. I use 'e' for getting into the container sometimes OK and sometime NOT OK. it's hardly to make a rule for the disable problem. But the bug definitely exists.
@WayneChang65 can you please read my comment above and check that your container has a shell?
I'm facing this right now and can necro-bump this issue.
docker exec -it your_container /bin/sh works fine in my situation and exec from within CTOP works for all the other containers that were start by docker-compose.
The only difference I have with this one container in particular, is that I start it with user: 1000:1000 from within compose. I suspect it has something to do with that. Maybe something similar is happening in lazydocker too https://github.com/jesseduffield/lazydocker/issues/350
