Created Docker container with Event Store running in it. A slight modification from the published Event Store container (I added an extra data volume for logs).
I think this might be new with Event Store 3.8, because it wasn’t a problem for me earlier, but it seems that now when we spin up the container and browse to http://192.168.99.100:2113/ (that is the IP of the Docker VM on Windows installation), it redirects to http://0.0.0.0:2113/web/index.html and then of course we get “This site can’t be reached on Chrome, with ERR_ADDRESS_INVALID”. I know Event Store must be responding to the request because of the way it tacks on the “/web/index.html” sub-path.
Notably, entering the following URL directly into the browser works perfectly: http://192.168.99.100:2113/web/index.html
The Dockerfile is almost the same as here: https://github.com/EventStore/eventstore-docker/blob/master/Dockerfile, but with the added “VOLUME /var/log/eventstore”
Here is the startup command:
docker run --name eventstore -d -v /data/EventStore:/var/lib/eventstore -v /logs/EventStore:/var/log/eventstore -p ``1113``:``1113 -p ``2113``:``2113 ourapp/eventstore
I suspect this might be related to (or causing) another issue with the container where we can’t seem to create a valid projection (I’ll create another thread with that issue just in case they’re unrelated).