-
-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
feat(dev): Upgrade zookeeper/kafka dev containers for Intel hosts #29293
Conversation
In #28574, we upgraded the versions of zookeeper/kafka to 6.x only for Apple arm64 hosts. When trying to use such version on Intel, it would fail because version 6.x requires specifying the path to `data` *absolutely* (see [docs][docs]), otherwise, you would get this error: > Command [/usr/local/bin/dub path /var/lib/kafka/data writable] FAILED ! If you don't rename the key of the moount bind, users with an existing set-up would not get the absolue path properly configured, thus, they would still face the issue (see [comment][comment]). In other words, people starting from scratch would have no issues. At the time, we decided to back things out and investigate later. This change reunites Intel and arm64 hosts. [docs]: https://docs.confluent.io/platform/current/installation/docker/operations/external-volumes.html#data-volumes-for-kafka-and-zk [comment]: #28574 (comment)
"environment": {"ZOOKEEPER_CLIENT_PORT": "2181"}, | ||
"volumes": {"zookeeper": {"bind": "/var/lib/zookeeper"}}, | ||
"volumes": {"zookeeper_6": {"bind": "/var/lib/zookeeper/data"}}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changing the key is what allows users that come from version 5.x to not require a fresh set up.
@avgupta456 would you mind testing it locally? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We are not using v6 for on-premise so kind of blind-accepting.
FYI, with this version, we can drop zookeeper:
I'm aware of that. I've added it to the backlog. |
In #28574, we upgraded the versions of zookeeper/kafka to 6.x only for Apple
arm64 hosts.
When trying to use such version on Intel, it would fail because version 6.x
requires specifying the path to
data
absolutely (see docs), otherwise, you would get thiserror:
If you don't rename the key of the moount bind, users with an existing set-up would not get
the absolue path properly configured, thus, they would still face the issue (see comment).
In other words, people starting from scratch would have no issues.
At the time, we decided to back things out and investigate later.
This change reunites Intel and arm64 hosts.