Open riveryong opened 6 years ago
Hi @riveryong . Please check the logs ( zookeeper.log ) to understand why Zookeeper doesn't start. You'll find them at http://localhost:3030/logs/
I got the same error. Can't connect to localhost:3030 - ERR_CONNECTION_REFUSED
Hi @charlesxucheng, yours is a different issue. If you are on windows, probably docker didn't expose the port at localhost, so you have to find the address that docker uses.
don't use --net=host
as docker currently has problems with it on windows.
try this instead:
docker run --rm -p 3030:3030 -p 9092:9092 -p 8081:8081 -p 8083:8083 -p 8082:8082 -p 2181:2181 landoop/fast-data-dev
--net=host
does not work for MacOs as well.
same problem on linux. in addition to the command shown above, you have to change the advertised host, otherwise you won't be able to connect.
docker run --rm -e ADV_HOST=localhost -p 3030:3030 -p 9092:9092 -p 8081:8081 -p 8083:8083 -p 8082:8082 -p 2181:2181 landoop/fast-data-dev
I had the same problem with Mac OSx 10.14.2 also. As advised by @danield137 and @aprooks I explicitly gave the following ports and it worked like a charm on http://127.0.0.1:3040/
docker run --rm -it -p 3181:3181 -p 3040:3040 -p 7081:7081 -p 7082:7082 -p 7083:7083 -p 7092:7092 -e ZK_PORT=3181 -e WEB_PORT=3040 -e REGISTRY_PORT=8081 -e REST_PORT=7082 -e CONNECT_PORT=7083 -e BROKER_PORT=7092 -e ADV_HOST=127.0.0.1 landoop/fast-data-dev
I had the same problem with Mac OSx 10.14.2 also. As advised by @danield137 and @aprooks I explicitly gave the following ports and it worked like a charm on http://127.0.0.1:3040/
docker run --rm -it -p 3181:3181 -p 3040:3040 -p 7081:7081 -p 7082:7082 -p 7083:7083 -p 7092:7092 -e ZK_PORT=3181 -e WEB_PORT=3040 -e REGISTRY_PORT=8081 -e REST_PORT=7082 -e CONNECT_PORT=7083 -e BROKER_PORT=7092 -e ADV_HOST=127.0.0.1 landoop/fast-data-dev
This fix worked for me on my Mac OSx 10.12.6 as well. Thanks @surysharma !
I had the same problem with Mac OSx 10.14.2 also. As advised by @danield137 and @aprooks I explicitly gave the following ports and it worked like a charm on http://127.0.0.1:3040/
docker run --rm -it -p 3181:3181 -p 3040:3040 -p 7081:7081 -p 7082:7082 -p 7083:7083 -p 7092:7092 -e ZK_PORT=3181 -e WEB_PORT=3040 -e REGISTRY_PORT=8081 -e REST_PORT=7082 -e CONNECT_PORT=7083 -e BROKER_PORT=7092 -e ADV_HOST=127.0.0.1 landoop/fast-data-dev
I got the same issue, but for schema-registry to run lensesio/box, it's weird, everything was ok yesterday
2019-12-25 06:50:39,867 INFO exited: schema-registry (exit status 1; not expected) 2019-12-25 06:50:40,306 INFO spawned: 'schema-registry' with pid 1330 2019-12-25 06:50:41,463 INFO success: schema-registry entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
then I had to add -e REGISTRY_PORT=8081 -e BROKER_PORT=7092
to my command
docker run -e ADV_HOST=127.0.0.1 -e EULA="https://dl.lenses.io/d/?id=xxx" --rm -p 3030:3030 -p 9092:9092 -p 2181:2181 -p 8081:8081 -e REGISTRY_PORT=8081 -e BROKER_PORT=7092 lensesio/box
windows10, I give 6GB to docker, when I run:
docker run --net=host landoop/fast-data-dev
it is output:do any one has same problem?