Open simplesteph opened 3 years ago
Facing similar issue. Btw, all other images like schema registry, connect works with tag 5.5.3, but confluentinc/ksqldb-server fails on 5.5.3 fails with same dub error. see https://forum.confluent.io/t/change-zookeeper-user-id-for-kafka-docker-images/1075
I'm having the same problem. Is there any progress on this issue, or maybe a workaround etc.? And if not, is there any way for us to help?
Same issue here.
I'm seeing this with Confluent's zookeeper
component:
host$ docker logs zookeeper
===> User
uid=1000(appuser) gid=1000(appuser) groups=1000(appuser)
===> Configuring ...
===> Running preflight checks ...
===> Check if /var/lib/zookeeper/data is writable ...
Command [/usr/local/bin/dub path /var/lib/zookeeper/data writable] FAILED !
Hi! Any reasonable workaround?
Hi! Any reasonable workaround?
Hi @jeromerg, what I am doing is, taking reference of docker image adding RUN statement to own by root group. Why I am doing this -
volumes: - ./zk-single-kafka-single/kafka1/data:/var/lib/kafka/data
Please make sure container has write permission on the host directory:
chown -R 1000:1000 ./zk-single-kafka-single/kafka1/data
any update on this?
On windows, I tried Cleaning up docker, reinstalling, using different image etc. But then I simply changed the name of directory to new directory and it started working.
volumes:
- ./storage/newzoodata:/var/lib/zookeeper/data
- ./storage/newzoolog:/var/lib/zookeeper/log
I have to admit that I had simply deleted older directory and it stopped working since then. So may be something to do with reuse of directories.
The issue to focus on is the "volumes" part of the docker-compose file
I'm using the Ubuntu 20.04 AMI from AWS to reproduce the issue
Using this docker-compose file, things fail:
See how the version used is confluent/cp-kafka:6.1.0
If I remove these two lines, things work:
But obviously, these lines are needed to externalize the data file of the docker image.
If I use the version 6.0.2, same outcome.
If I use the version 5.5.3, things work as expected:
See the log output:
So something changes at 6.x and I don't know what or how to fix it. The goal is to externalize the data directory
Cheers Stephane