PORT 2375 / TCPInfrastructure & CloudExposure Risk: Critical

Port 2375: Docker Daemon — Unencrypted Docker Remote API

Unauthenticated Docker daemon socket over TCP. Exposing this publicly grants instant root host takeover.

Default Service

Docker Daemon

Process: dockerd

Transport Protocol

TCP

IANA Registered Port 2375

Docker Port Flag

-p 2375:2375

Container to Host Mapping

How to Check & Kill Process on Port 2375 (EADDRINUSE Fix)

macOS & Linux (lsof / kill)

# Find process using port 2375
sudo lsof -i :2375

# Instantly kill process on port 2375
lsof -ti:2375 | xargs kill -9

Windows (PowerShell & CMD)

# Find PID listening on port 2375
netstat -ano | findstr :2375

# Force kill by PID
taskkill /PID <PID_NUMBER> /F

Cross-Platform Node.js One-Liner

# Kill port 2375 via npx
npx kill-port 2375

# Or diagnose via Castov CLI
npx castov fix "EADDRINUSE :::2375"

Linux Firewall (UFW) & Connectivity Test

# Test if port 2375 is reachable
nc -zv localhost 2375

# Allow or deny port 2375 in UFW
sudo ufw allow 2375/tcp

Frequently Asked Questions about Port 2375

What is Port 2375 used for?

Port 2375 is the standard network port for Docker Daemon (Unencrypted Docker Remote API) operating over TCP. The typical system daemon or process is dockerd.

How do I kill a process running on Port 2375 (EADDRINUSE)?

On macOS and Linux, run: lsof -ti:2375 | xargs kill -9 (or npx kill-port 2375). On Windows PowerShell/CMD, run: netstat -ano | findstr :2375 and then taskkill /PID <PID> /F.

Is it safe to expose Port 2375 to the internet?

Port 2375 has a Critical security risk profile. Unauthenticated Docker daemon socket over TCP. Exposing this publicly grants instant root host takeover.