-
Notifications
You must be signed in to change notification settings - Fork 19
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
unable to create topics in Redpanda #2
Comments
Are you running the commands from inside or outside the container? https://www.youtube.com/watch?v=sJ4mRqHAtjI |
Thanks for the quick feedback. I ran the |
Hi there. I was not having any luck getting the environment up on my work machine. So on my personal Mac I installed Docker for Desktop and followed the instructions and the environment came up without an issue. I will check back on my work machine tomorrow and get some screen grabs of the errors I'm seeing. There is obviously some kind of issue if using other container runtimes. Thanks. |
@hectorrios please do share some screenshots. |
Hi @polyzos Thank you. Here is a screenshot I grabbed just now. It seems like it's not possible to elect a leader for the cluster based on the messages. I'm using the docker runtime available from the Colima project https://github.com/abiosoft/colima as we don't have Docker for Desktop licenses here at work. ![]() |
I'm not familiar with that colima, but since the cluster spin up I suspect the issue should be elsewhere. |
Seems like docker doesn't have permissions there. |
I had an issue bringing up the docker compose on Ubuntu 20.04. I tweaked the docker-compose.yaml to use a user defined network (the container name dns resolution was failing - redpanda:9092 was failing)... (I had to change the extension to .txt as I could not upload file with .yaml extension) |
Hi there
I started up the Docker environment and everything came up fine from what I can tell. However when I try to execute the redpanda setup script I get the following message.
I also tried running the
rpk cluster info
from the container and received the following.I'm running on an Intel based MacBook Pro and using
colima
in place of Docker Desktop, if that makes a difference.Thank you
The text was updated successfully, but these errors were encountered: