ramalama serve is not checking if the port is available before running the command

[benoitf]

Being a pretty dumb user, I don't care the port where the model will be served. It can be a random port as it's being displayed

1. using 8080 as a default port is quite challenging because as a developer, I have tons of app that I start that are already using this port.
   (so picking up a port different than 8080 can increase the "first attempt succeed"

2. most of the cli launchers detect that the port is in use and is serving the app using a basic '+1' on the default port

so If I launch 2 serve commands, it won't fail (unless I specify a port number and in that case yes I expect it fails if it's already taken but without specifying a port number I will assume the tool is picking one for me that works)

here is the current error message:

Error: preparing container ee6f2c8cd4377db38836b25c7523147a2383bcd9d86f22db0446b15212bd5bfb for attach: cannot listen on the TCP port: listen tcp4 :8080: bind: address already in use

[ericcurtin]

2. makes sense to me, keep trying ports and increment until an available one is found

[rhatdan]

We would need to somehow display the port.