The socket issue and port allocation issue are unrelated to the Local 2.3.2 upgrade. These are Docker issues. Going to the menu in the top-left and then “Restart Local’s Machine” should resolve those errors.
Also, please try the test build of 2.3.3 here. It should resolve some of the other issues you reported in other threads. What to do if your recently updated 1.3 environment website doesn't start (and you want to go back)
If you’re still seeing the maintenance message, delete the .maintenance file in the site’s app/public folder. See Briefly unavailable for scheduled maintenance. Check back in a minute for more details.