Skip to content
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.

Sign up for GitHub

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

Jump to bottom

kafka-connect-ui exit(2) when running on linux #111

Open
iamacoderguy opened this issue Jun 11, 2021 · 5 comments · May be fixed by #116
Open

kafka-connect-ui exit(2) when running on linux #111

iamacoderguy opened this issue Jun 11, 2021 · 5 comments · May be fixed by #116

Comments

@iamacoderguy
Copy link

Hi team,

When lunching the image landoop/kafka-connect-ui on linux, it exited with error code = 2. The logs are as following

Landoop Kafka Connect UI
Visit <https://github.com/Landoop/kafka-connect-ui/tree/master/docker>
to find more about how you can configure this container.

Enabling proxy. You can disable this via PROXY=false.
Note: if you use a PORT lower than 1024, please note that kafka-connect-ui can
now run under any user. In the future a non-root user may become the default.
In this case you will have to explicitly allow binding to such ports, either by
setting the root user or something like '--sysctl net.ipv4.ip_unprivileged_port_start=0'.

Activating privacy features... done.
http://0.0.0.0:8000
panic: runtime error: slice bounds out of range

goroutine 1 [running]:
github.com/mholt/caddy/vendor/github.com/miekg/dns.ClientConfigFromFile(0xb5fb42, 0x10, 0x0, 0x0, 0x0)
        /var/folders/d4/3d8k5bgd62v9h2c5f05xkyx80000gn/T/gopath_02-19-2255.179888757/src/github.com/mholt/caddy/vendor/github.com/miekg/dns/clientconfig.go:86 +0x9c4
github.com/mholt/caddy/vendor/github.com/xenolf/lego/acme.getNameservers(0xb5fb42, 0x10, 0xf79b40, 0x2, 0x2, 0xbe7720, 0xc42007e2d0, 0xc420061f58)
        /var/folders/d4/3d8k5bgd62v9h2c5f05xkyx80000gn/T/gopath_02-19-2255.179888757/src/github.com/mholt/caddy/vendor/github.com/xenolf/lego/acme/dns_challenge.go:40 +0x4d

Our docker compose configuration:

connect-ui:
    image: landoop/kafka-connect-ui
    container_name: connect-ui
    depends_on:
      - connect
    ports:
      - "8001:8000"
    environment:
      - "CONNECT_URL=http://connect:8083"

It's running well when using docker in windows with WSL.

Do you have any suggestions?

Thank you,
@spirit986
Copy link

spirit986 commented Jul 7, 2021 •
edited

I am having exactly the same issue.
While troubleshooting I found out that running the container without docker-compose actually works.

So this works:

docker run -d -it -p 8083:8000 \
 -e "CONNECT_URL=http://10.10.0.10:8083" \
 landoop/kafka-connect-ui

But within docker-compose throws in the error.

Edit:
Continuing my troubleshooting I have this service running with docker-compose on another server which runs Ubuntu 18. The error I am getting on Ubuntu 20 and docker-compose.
Changing to an older docker-compose version didn't have any effect.

@user578
Copy link

user578 commented Sep 17, 2021

The workaround is to add this line

network_mode: bridge

for service in docker-compose.yml

@wilius
Copy link

wilius commented Oct 4, 2021

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.

version: '3.6'
services:
  ...
  kafka_connect_ui:
    container_name: kafka_connect_ui
    image: landoop/kafka-connect-ui
    ports:
      - "9001:8000"
    environment:
      CONNECT_URL: http://connect1:8083
    depends_on:
      - connect1
    network_mode: bridge
    extra_hosts:
      - "connect1:host-gateway"
  connect1:
    image: debezium/connect:1.5
    volumes:
      - connect
    ports:
      - "8083:8083"
    depends_on:
      - kafka1
      - kafka2
      - kafka3
    environment:
      - BOOTSTRAP_SERVERS=kafka1:9092,kafka2:9092,kafka3:9092
      - GROUP_ID=1
      - CONFIG_STORAGE_TOPIC=my_connect_configs
      - OFFSET_STORAGE_TOPIC=my_connect_offsets
      - STATUS_STORAGE_TOPIC=my_connect_statuses
    ....

@looopTools
Copy link

I am also experiencing this on Ubuntu 20.10 are there an alternative solution to running it in bridge mode?

nov30th added a commit to nov30th/kafka-connect-ui that referenced this issue Dec 16, 2023
@nov30th
fixed unable to start with caddy, panic: runtime error: slice bounds …
ce9bf84 
…out of range

fixed lensesio#111
@nov30th nov30th linked a pull request Dec 16, 2023 that will close this issue
Open
@nov30th
Copy link

nov30th commented Dec 17, 2023

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fixed unable to start with caddy, panic: runtime error: slice bounds … nov30th/kafka-connect-ui
6 participants
@wilius @looopTools @user578 @spirit986 @nov30th @iamacoderguy