You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm running Mesos 0.28.2 and I just started the standalone-0.1.4 image with: docker run -p 33000:33000 -e MESOS_ENDPOINT=http://master.mesos:5050 capgemini/mesos-ui:standalone-0.1.4
The output of the container shows some "Starting messages" and the last message says "Finied 'server' after 1.35s".
I try to curl localhost:33000 and also try to browse to my_server:33000 and I get nothing. When I curl, I get curl: (56) Recv failure: Connection reset by peer.
Any thoughts/ideas? I notice the README in the gihtub repo instructions is different than on docker hub, not sure which is correct. Also, on docker hub I just noticed it is compatible with mesos 0.23....is that accurate?
The text was updated successfully, but these errors were encountered:
Hi,
the output message is expected and correct but the server is listening on 5000 inside the container https://github.com/Capgemini/mesos-ui/blob/master/src/config/config.js#L4 so docker run -p 33000:33000 is never going to give you access to the server from the host. Instead you should docker run -p 33000:5000, then try to curl localhost:33000
Thanks!
I'm running Mesos 0.28.2 and I just started the standalone-0.1.4 image with:
docker run -p 33000:33000 -e MESOS_ENDPOINT=http://master.mesos:5050 capgemini/mesos-ui:standalone-0.1.4
The output of the container shows some "Starting messages" and the last message says "Finied 'server' after 1.35s".
I try to curl localhost:33000 and also try to browse to my_server:33000 and I get nothing. When I curl, I get
curl: (56) Recv failure: Connection reset by peer
.Any thoughts/ideas? I notice the README in the gihtub repo instructions is different than on docker hub, not sure which is correct. Also, on docker hub I just noticed it is compatible with mesos 0.23....is that accurate?
The text was updated successfully, but these errors were encountered: