-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
[bitnami/kafka] 3.5.1 Error SSL Handshake at Kraft Broker Startup with Docker Compose Configuration #53286
Comments
Docker versionClient: Docker Engine - Community
Version: 24.0.5
API version: 1.43
Go version: go1.20.6
Git commit: ced0996
Built: Fri Jul 21 20:36:32 2023
OS/Arch: linux/amd64
Context: default
Server: Docker Engine - Community
Engine:
Version: 24.0.5
API version: 1.43 (minimum version 1.12)
Go version: go1.20.6
Git commit: a61e2b4
Built: Fri Jul 21 20:35:32 2023
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: 1.6.24
GitCommit: 61f9fd88f79f081d64d6fa3bb1a0dc71ec870523
runc:
Version: 1.1.9
GitCommit: v1.1.9-0-gccaecfc
docker-init:
Version: 0.19.0
GitCommit: de40ad0 Docker Compose versionDocker Compose version v2.21.0 |
Please @javsalgar your help with this issue. |
This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback. |
Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary. |
I'm facing the same error when running on 3.5. In fact kafka runs fine for me on
|
Hi, the original issue is quite old. Could you please share information about the specific environment you are using to run your Kafka deployment? I.e. Helm chart parameters, versions... |
Name and Version
bitnami/kafka:3.5.1
What architecture are you using?
None
What steps will reproduce the bug?
Using image docker.io/bitnami/kafka:3.5.1 and docker compose
On Red Hat Enterprise Linux release 8.8 (Ootpa) server
Using the configuration of docker-compose-cluster.yml file and Security parameters as described in https://github.com/bitnami/containers/tree/main/bitnami/kafka#security
Configuration in docker compose yaml file used:
Start the broker service with docker compose
What is the expected behavior?
What is expected is that the broker server starts successfully.
What do you see instead?
The broker server crashes and terminates with status code 1.
The log is the following:
Additional information
The keystores were generated using wildcard certificate for the domain "*.domain.com" which is the domain assigned to the hostname.
The text was updated successfully, but these errors were encountered: