AsciiSpec Server causes issues in Docker container

[bsmith-n4]

#68 causes some issues with Docker

First, it complains about the ports not being accessible.
See http://build-master.corp.numberfour.eu:8080/view/Documentation/job/OPR_spec_multibranch/job/OPR-1185/24/console

It's possible to specify exposed ports using -p;

docker run --rm -t -p 45115:45115 -v ...workspace:rw docker.corp...asciispec:0.0.4 $*

But in this case, the following error occurs:

docker: Error response from daemon: driver failed programming external connectivity on endpoint endpoint_name
Bind for 0.0.0.0:45115 failed: port is already allocated.

[torstenkraemer]

Console output referenced above states:

/asciispec/bin/asciispec: line 131: /dev/tcp/localhost/45115: Connection refused

I wonder what service should be running at this port: 45115

[torstenkraemer]

Found it with https://github.com/NumberFour/asciispec/search?utf8=%E2%9C%93&q=45115&type=

The Asciispec-server itself: https://github.com/NumberFour/asciispec/blob/84a88b3bec06cb235bb369def2f781eea35adf53/src/main/java/eu/numberfour/asciispec/cli/AsciiSpecServer.java

So it's not an external service but internally to the docker-container.
Hence, @bsmith-n4 mounting something from outside the docker-container is not the solution.

[torstenkraemer]

Looking at the asciispec executable I see that the whole server-functionality was introduced by IDE-2736 and related commits (e.g. 51ad7fe)

@mmews-n4 I see two ways to tackle the issue:

• test the approach within the docker-container
  OR
• make a separate container for the server and wire the two docker-containers together (via docker-compose) to get the task done.

[mmews-n4]

For the time being, we can use the direct switch to call asciispec without the server. To make asciispec executable in Docker, etc. there is a new ticket here: https://jira.numberfour.eu/browse/IDE-2754

[bsmith-n4]

published v0.0.5 aspec docker image with temporary workaround for this:
https://github.numberfour.eu/NumberFour/dockerfiles/pull/19