web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Small and medium business | Business Central, N...
Answered

Business Central in a Docker container not responding: "bcserver took too long to respond"

(0) ShareShare
ReportReport
Posted on by 262
All of a sudden my BC Docker containers stopped working. All of them, just don't respond anymore. Chrome dev tools show no response at all coming from the containers. Still the containers are active and perfectly responsive, except the on the http port.
I can download symbols in VS Code and publish packages - no problem. I can start a PowerShell session with "Enter-BCContainer" or "Open-BCContainer", also works. All BC endpoins are active, Invoke-WebRequest works perfectly when I send a request to the BC service in a container session. For example "http://localhost:7049/dev/packages", "http://localhost:7049/devhealth", or "http://localhost:7046/bc/client/health" - all works.
"Invoke-WebRequest http://localhost/bc" - no response.
The same client/health endpoint is also unreachable if the request goes via IIS: "Invoke-WebRequest http://localhost/bc/client/health" - no response.
Web site on IIS is running, application pool is active, I could not find anything wrong with the web server configuration. Default web site on port 8080 also responds without any issues, so I suppose this must be something with the BC web client, but I'm out of ideas. I suspect a recently installed Windows security update could cause this, but reverting the updates did not solve the problem. And of course I tried to delete and recreate the container - still the same result. After spending a weekend trying to pinpoint the issue, I still have no idea where the problem is.
Has anyone seen something similar? Any ideas what else I can try?
I have the same question (1)
  • Suggested answer
    Khushbu Rajvi. Profile Picture
    20,275 Super User 2025 Season 2 on at
  • Alexander Drogin Profile Picture
    262 on at
    @Khushbu Rajvi. Thanks for the suggestion, but I can't see how I can apply it to my specific problem.
  • Verified answer
    Alexander Drogin Profile Picture
    262 on at
    If somebody runs into this problem: changing the container isolation from process to hyperv solved the problem.
    My configuration: Windows 11 pro, Docker Desktop on WSL 2. I used to run all containers in process isolation, but since updating Windows to version 24H2 I am unable to connect to the web client in any existing container. I could not find the root cause, but recreating the containers with isolation = hyperv resolved it.
  • hbulens Profile Picture
    7 on at
    @Alexander Drogin what version of Docker are you running? The latest version of Docker Desktop doesn't seem to have that config option any more.
  • Alexander Drogin Profile Picture
    262 on at
    I used BCContainerHelper to create the container.
    I think my Docker Desktop was 4.30.0, but I'm not really sure, at the moment, I don't have access to the laptop where I ran it.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > Small and medium business | Business Central, NAV, RMS

#1
OussamaSabbouh Profile Picture

OussamaSabbouh 3,229

#2
Jainam M. Kothari Profile Picture

Jainam M. Kothari 1,867 Super User 2025 Season 2

#3
YUN ZHU Profile Picture

YUN ZHU 1,153 Super User 2025 Season 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans