Open leopoldstrauch opened 6 years ago
I think this issue typically occurs when the docker instance does not have enough memory allocated to it. i.e. see image at http://lenses.stream/developers-guide/dev-environment/index.html#faq and try to allocate i.e. 4GB to your Kafka, ZK, Sh. Reg, Connect and other services
I managed to started it by setting ADV_HOST and Ports manualy:
docker run --rm -it \
> -p 2181:2181 -p 3030:3030 -p 8081:8081 \
> -p 8082:8082 -p 8083:8083 -p 9092:9092 \
> -e ADV_HOST=127.0.0.1 \
> landoop/fast-data-dev
but i will check your link too thanks :)
I was getting this too when trying to start the image in a docker-compose.yml file, but my colleagues were not. The only difference we could come up with is that I am macOS High Sierra, and they were not.
At any rate, I was able to solve by adding to my docker-compose for kafka:
volumes:
- /var/run/docker.sock:/var/run/docker.sock
@leopoldstrauch 's suggestion fixed the issue on my side (docker for macos high sierra), I wonder why this is happening
I also had the same issue, but when statistically setting the port (I'm using a mac) no issues.
I had the same issue on my Mac after a bit of investigation it appears that "--net=host" which should use the hosts network directly doesn't work. But on closer reading "The host networking driver only works on Linux hosts". Because Mac Docker runs inside a virtual machine so when it binds to the "host" network adapter its binding to the virtual machine and not to your Mac's network adapter.
Full discussion here:
https://forums.docker.com/t/should-docker-run-net-host-work/14215
Every time i start the docker container with docker run --rm --net=host landoop/fast-data-dev some components crash periodicaly Any ideas?