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

Ctrl+C does not stop/kill Docker running the docs #897

Open
mlvandijk opened this issue Jul 3, 2023 · 2 comments
Open

Ctrl+C does not stop/kill Docker running the docs #897

mlvandijk opened this issue Jul 3, 2023 · 2 comments
Labels
🐛 bug Defect / Bug

Comments

@mlvandijk
Copy link
Member

👓 What did you see?

Am running the project as mentioned in the README, running the script with with command mentioned: ./docker_shell.sh.
Once Docker is started I get console output including the following at the end.

Web Server is available at http://localhost:1313/ (bind address 0.0.0.0)
Press Ctrl+C to stop

However, pressing Ctrl+C does nothing.
Instead I have to go to a different console window, type docker ps to find the container and then stop/kill it.

✅ What did you expect to see?

I'd expect the docker container to be stopped/killed using the provided command (or, if that command no longer works, be provided with the correct command).

📦 Which tool/library version are you using?

Mac OS 13.4
IntelliJ IDEA 2023.1.3 (Ultimate Edition)
Docker Desktop 4.10.1 (82475)

🔬 How could we reproduce it?

Run ./docker_shell.sh
Press Ctrl+C

📚 Any additional context?

@mlvandijk mlvandijk added the 🐛 bug Defect / Bug label Jul 3, 2023
@ciaranmcnulty
Copy link

ciaranmcnulty commented Jul 5, 2023

Weird, this works for me on:

MacOS 13.0
IntelliJ PhpStorm 2023.1.3
Docker Desktop 4.20.1

Seems a close match, I'm behind on MacOS but ahead of you on Docker Desktop (I assume the IntelliJ terminals are roughly the same).

Try upgrading Docker Desktop? I'll update my MacOS and see if it breaks anything.

Also what architecture are you on (Intel/Apple Silicon)?

@ciaranmcnulty
Copy link

This is still the case after I update to MacOS 13.5 so must be some other factor

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

No branches or pull requests

2 participants