Process port conflicts on container start in a user friendly way #6312
Description
Description
On add-on start, if a port is already occupied, Docker raises a common error, but uses a rather specific text. The text however is somewhat long and annoying to parse.
Ideally we parse such common errors properly and turn it into a custom named exception with the parsed information as property (like port).
There are quite some add-ons which have multiple copies of the same add-on with different quality (e.g. stable/beta/dev). Such add-ons seem to appear often in our Sentry logs (e.g. ESPHome/Zigbee2MQTT).
Additional context
No response