-
Notifications
You must be signed in to change notification settings - Fork 129
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
kafka-connect-ui exit(2) when running on linux #111
Comments
I am having exactly the same issue. So this works:
But within docker-compose throws in the error. Edit: |
The workaround is to add this line
for service in docker-compose.yml |
the solution of @user578 is also working. the problem of it is that it creates a new, isolated network for kafka-connect-ui and if you have a kafka-connect instance on docker-compose file. it can't be accessible by kafka-connect-ui. to overcome this issue, my setup below worked well.
|
I am also experiencing this on Ubuntu 20.10 are there an alternative solution to running it in bridge mode? |
p.s for who don't wanna build docker and simple want this issue fixed docker: base on the latest version currently, I've built one docker pull nov30th/kafka-connect-ui:v1.0.0 |
Hi team,
When lunching the image landoop/kafka-connect-ui on linux, it exited with error code = 2. The logs are as following
Our docker compose configuration:
It's running well when using docker in windows with WSL.
Do you have any suggestions?
Thank you,
The text was updated successfully, but these errors were encountered: