This issue has been fixed. Once it's in stable ChromeOS, there's no need for us to use specific ports by default (which can result in binding errors if they're taken):

https://bugs.chromium.org/p/chromium/issues/detail?id=848063