You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Output of compose log:
...
Creating zookeeper ... error
ERROR: for zookeeper Cannot start service zookeeper: Ports are not available: listen tcp 0.0.0.0:2181: bind: An attempt was made to access a socket in a way forbidden by its access permissions.
ERROR: for zookeeper Cannot start service zookeeper: Ports are not available: listen tcp 0.0.0.0:2181: bind: An attempt was made to access a socket in a way forbidden by its access permissions.
ERROR: Encountered errors while bringing up the project.
Environment
GitHub branch: 7.0.0-post
Operating System: Windows 10
Version of Docker: Docker Desktop 3.0.0 / 4.2.0
Version of Docker Compose: version 1.27.4, build 40524192 / 1.29.2, build 5becea4c
Updated Docker Desktop, same issue
The text was updated successfully, but these errors were encountered:
Description
Error starting zookeeper on docker-compose up.
May be Docker issue docker/compose#7188
Update
After upgrading Docker Desktop to 4.2.0 and rebooting machine, was able to get the instance to start; could be timing issue.
curl --silent --output docker-compose.yml
https://raw.githubusercontent.com/confluentinc/cp-all-in-one/7.0.0-post/cp-all-in-one/docker-compose.yml
docker-compose up -d
Troubleshooting
Docker Issue: Port conflict with multiple "host::port" services
Output of compose log:
...
Creating zookeeper ... error
ERROR: for zookeeper Cannot start service zookeeper: Ports are not available: listen tcp 0.0.0.0:2181: bind: An attempt was made to access a socket in a way forbidden by its access permissions.
ERROR: for zookeeper Cannot start service zookeeper: Ports are not available: listen tcp 0.0.0.0:2181: bind: An attempt was made to access a socket in a way forbidden by its access permissions.
ERROR: Encountered errors while bringing up the project.
Environment
Updated Docker Desktop, same issue
The text was updated successfully, but these errors were encountered: