Fixing the docker image

[sirixdb]

Fixing the docker image

[JohannesLichtenberger]

The verticle wants to communicate with Keycloak on port 8080, but Keycloak is running within another docker container for instance.

[JohannesLichtenberger]

Seems to be Windows related, the --network=host option maybe because of the additional VM doesn't seem to work, same exception with docker run --network=host -t -i -p 9443:9443 sirixdb/sirix

[kmjayadeep]

Related to #51. I cannot proceed with that unless docker file itself is fixed. So I'm looking into this.
According to the current dockerfile, the jar file must be built first before building the container. Shouldn't we doing this in the container itself, probably as a multi stage build?

[JohannesLichtenberger]

That would be great. However, I'm sadly no Docker expert. But I think the Dockerfile itself now works with Linux at least, thanks to another contribution.

And we should publish on Docker Hub again, I think. I don't remember why I disabled the automatic deployment images for SNAPSHOTs.

But if you can help with the multistage Docker image, that would be great. I think it was simply mvn package or something like that.