Spaces in socket path stop docker from starting

Docker Desktop for Mac
1

Expected behavior

The GUI tries to use the docker socket, but does not deal with whitespace in the socket path. I can only assume it is resolving ~/Library which should then either be interpolated correctly, or whitespace commented out?

Actual behavior

The client crashes, and tries 100 times to connect to the docker daemon via the socket.

Information

I know you shouldn’t have a space in a unix username, and generally spaces are a terrible idea in file paths for this exact reason, but its a cooperate laptop linked to AD and it cannot be changed.

Steps to reproduce the behavior

  1. Create a user with a space in their name in osx
  2. Fails to start docker gui.