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.

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

Open
hectorrios opened this issue Jun 14, 2023 · 9 comments
Open

unable to create topics in Redpanda #2

hectorrios opened this issue Jun 14, 2023 · 9 comments

Comments

@hectorrios
Copy link

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.

unable to create topics [accounts]: unable to dial: dial tcp 127.0.0.1:9092: connect: connection refused

I also tried running the rpk cluster info from the container and received the following.

unable to request metadata: unable to dial: dial tcp 127.0.0.1:9092: connect: connection refused

I'm running on an Intel based MacBook Pro and using colima in place of Docker Desktop, if that makes a difference.

Thank you

@polyzos
Copy link
Owner

polyzos commented Jun 14, 2023

Are you running the commands from inside or outside the container?
Also if you run docker ps do you see the redpanda container running?

https://www.youtube.com/watch?v=sJ4mRqHAtjI
I created this video to help with the environment setup. Are you running into issues while following that?

@hectorrios
Copy link
Author

Thanks for the quick feedback. I ran the rpk cluster info from inside the container and the the shell script from my host. I wasn't aware of the video, let me go through that and report back. Thanks again!

@hectorrios
Copy link
Author

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.

@polyzos
Copy link
Owner

polyzos commented Jun 15, 2023

@hectorrios please do share some screenshots.
I wanna help and unblock you asap

@hectorrios
Copy link
Author

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.

Screenshot 2023-06-15 at 11 38 29

@polyzos
Copy link
Owner

polyzos commented Jun 15, 2023

I'm not familiar with that colima, but since the cluster spin up I suspect the issue should be elsewhere.
Is there any chance you have a logs directory in place that is corrupted maybe? Can you try deleting the logs directory that is created when the container starts and try rerunning to make sure there isn't issue with that?

@hectorrios
Copy link
Author

The log directories looked fine, but I decided to re-clone the repo and tried again to bring up the environment. Now, the environment is coming up at all and erroring out due to a file permission error when trying to bring up the Flink JM (see screenshot).

Screenshot 2023-06-15 at 12 30 54

@polyzos
Copy link
Owner

polyzos commented Jun 15, 2023

Seems like docker doesn't have permissions there.
Some workarounds could be to comment the volume mounts inside the docker-compose file, add permissions to the folder with chmod 755 <folder-name>, or check the docker desktop and give permissions to that path.

@atulkhot
Copy link

atulkhot commented Aug 11, 2023

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)
I was able to proceed after that without any issues...

docker-compose-yaml.txt

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants