Closed dicesare closed 4 years ago
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
comment.
Stale issues will be closed after an additional 30d of inactivity.
Prevent issues from auto-closing with an /lifecycle frozen
comment.
If this issue is safe to close now please do so.
Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows. /lifecycle stale
Closed issues are locked after 30 days of inactivity. This helps our team focus on active issues.
If you have found a problem that seems similar to this, please open a new issue.
Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows. /lifecycle locked
Expected behavior
Actual behavior
Information
Windows Version:OS: Windows 10 Pro Edition: Professional Id: 1809 Build: 17763 BuildLabName: 17763.1.amd64fre.rs5_release.180914-1434
Docker Desktop Version: Version: 2.1.0.5 (40693) Channel: stable
Are you running inside a virtualized Windows e.g. on a cloud server or on a mac VM:
Steps to reproduce the behavior
Hello, while my container is in operation (using Kitematic) I cannot access central business from the browser (timeout is exceeded). after the stop of my container, I execute the command: docker start -i "container id". and I end up with this following information: