Bind for 0.0.0.0:8100 failed: port is already allocated event after creating a new web project with docker

Wappler General Need Help
1

Wappler Version : 6.0.0
Operating System : Windows 11
Server Model: Node
Database Type: Postgres
Hosting Type: Local Docker

Expected behavior

After creating a new web project any existing web projects utilizing Docker should stop running and the new project should start.

Actual behavior

I receive the following on initial startup of the new project and every time I attempt to restart it. Bind for 0.0.0.0:8100 failed: port is already allocated

Here’s what the containers look like. Even if I stop all of them manually and then attempt to start either of the web projects I encounter the same error.

image
image1678×969 103 KB

How to reproduce

Not sure how to replicate.

2

Any update on this? I’ve run into similar issue with Docker few times.

In my case, the project launches fine but the moment I edit anything on the page and save changes, Wappler seems to “lose connection” with Docker. When I tried to preview the page in browser, it keeps loading with blank page. Doing system check on Wappler doesn’t detect any error with Docker though.

Anyway I tried to manually restart the container in Docker and I get this error in Docker:

Cannot restart Docker Compose application. Reason: compose [restart] exit status 1. Container neu__development-db-1 Restarting Container neu__development-web-1 Restarting Error response from daemon: Cannot restart container 996ccecccc8134456ghbce0a8e4300cc19ffcf9aff172dd6ae5ca1a3a9c5c713f56: container 996ccecccc81 PID 433 is zombie and can not be killed. Use the --init option when creating containers to run an init inside the container that forwards signals and reaps processes

I had to kill Docker in Task Manager and launch it again to resolve the problem.

Wonder if this is actually a Wappler error or something to do with Docker. I’m on latest version of Docker.

Wappler Version: 6.0.2 (Stable)
Operating System: Windows 11
Docker: 4.26.0
Server Model: Node
Database Type: Postgres
Hosting Type: Local Docker

3

Update:

The issue seemed to have resolved after I switch to Beta Channel. Not sure why…

4

Well if docker is having problems with a container and cannot quickly stop it when you switch projects for example, it can become a zombie container holding the port open.

Usually this is resolved by manually killing the faulty container or restarting docker desktop or your pc.