Docker
Docker Desktop failed to start because the Unix socket path was too long
[vpnkit-bridge][F] listen unix <HOME>/Library/Containers/com.docker.docker/Data/http-proxy-control.sock: bind: invalid argument
Docker Desktop could not create required Unix sockets because the home directory path exceeded the platform socket path length limit on Mac or Linux.
Observed message
[vpnkit-bridge][F] listen unix <HOME>/Library/Containers/com.docker.docker/Data/http-proxy-control.sock: bind: invalid argument
Why it happens
- The home directory path is too long for Docker Desktop's Unix socket files.
- Docker Desktop cannot create required internal sockets within the platform path-length limit.
How to fix it
- Use a shorter username or home directory path.
- Restart Docker Desktop after reducing the effective socket path length.
