-
Notifications
You must be signed in to change notification settings - Fork 55
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
Failed to initialize Metadata client #21
Comments
Hello, To setup rancher-server with RAP : you can start Rancher Server like that : Then you can go to ADMIN > SETTING >> Add a Catalog part : Then go to CATALOG and add Rancher Active Proxy Stack And it should start Rancher Active Proxy ! Do not hesitate , if you need some more information. |
Thanks for your response @adi90x! Can you elaborate on what part of your command automatically adds a host? |
No part of the command add a host. |
I recommend not using docker-compose, but using the Rancher catalogue entry directly. |
I understand. Your comment sounded like your command would start a host as well :). Thanks a lot for your help :). |
If you have |
Thanks a lot! I will try this out and ping you up if I need further help 👍 . |
A question came up: |
I started rancher-server with your command and then added a host to the static IP and port 8080. I want to reach rancher-server on my.domain.com, is this not possible with RAP? |
it is , when you start the rancher-server containers at the beggining , you can add rap label to it in the example it was : |
The label is already contained in the docker run command. Do I have to add it again while the container is running? |
Hi guys, I just found this interesting & still hot discussion, so let me summarize how I would do the setup without ssl ( in virtual box) and later with ssl somewhere out there..
Right? |
@dropfen No step 1 ! Setup rancher server as normal, grab the catalog, add it , fire a new RAP stack from the catalog. |
@adi90x I did just as you say, but it doesn't work. The rancher-server is on a different subnet than RAP and I don't see RAP recognizing the rancher-server container in the logs, when I restart it. |
@adi90x thx. I got it. If something goes wrong, I'll come back, hopefully not :) |
@dropfen If you can make this work (aka accessing the rancher-server via https on a domain with RAP container running on the same host) then please come back and describe how you did it |
That is my exact setup ! It should be working ! |
Can you Plesse show an example of rap container logs how it looks like if it Sees a New container with rap.host? Also what are the internal IP adresses of rancher-server and rap? (You can See that in infrastructure > containers. |
Hey, I got it up and running on VirtualBox at least :) My Setup: Container Host -> RancherOS
|
Hm. I will try again later completely from scratch. Maybe I've missed something. |
Its also important that your server/vm has enough capacities to run the server & the host. With 1GB of RAM it just crashed.. So now with 2GBs its at least running, but some people are saying, that after some time it eats all the memory and so on. So its not related to RAP, btw. thank you @adi90x, but rancher is not a small fancy toy for small projects. Actually, I am going to setup a complete GitLab Infrastructure on the same host as the server, and for production it will be some other host. I am planning to do it on a 6GB machine, and I am also not quite sure if its enough or not for the builds and so on. However Good luck @Braintelligence |
I'm running this stuff on a VM with 4 Xeon Cores and 16GB ECC RAM on a RAID SSD... Hardware is definitely not the problem. |
Ok, so I'm retrying from scratch. Let's make a history of everything I'm doing, so others won't run into the same problems. I'm running this on a ubuntu server VM with the latest docker and docker-compose. I killed all (also dangling) docker containers, volumes and images. I disabled the ufw firewall (even though I made it work with everything up till now). I have two scripts, so I don't need to type it everytime I want to fiddle around.
The other one is like this:
copied from the rancher-server.
@adi90x Any idea why no letsencrypt certificate is being fetched? |
I added /etc/nginx/conf.d to the bound volumes. The default.conf doesn't even contain anything about SSL connections. |
Wow, ok. So now... why does it need for another stack to spin up for RAP to recognize the rancher-server needs a letsencrypt certificate, too? |
@Braintelligence I finally finished the setup for my infra environment. To trigger the vhost and certs creation for rancher-server (without other services), I had to stop it, remove it, and run it again. When I then started Gitlab, it triggered the creation of the corresponding rap stuff immediately. |
Yeah, so it looks like you have to create another stack for RAP to be triggered for the rancher-server. Maybe this should be added to the readme for this use-case. |
good point 👍 |
Hi there.
I tried running RAP but when I fire docker-compose up I see this error in the logs:
Failed to initialize Rancher Metadata client: Get http://rancher-metadata/latest/version: dial tcp: lookup rancher-metadata on 127.0.0.11:53 no such host
I think this is due to using rancher-proxy without having a rancher-agent running.
My problem is, though, that I want to use a rancher-server and -agent on the same host and I need some best practice on what my initial docker-compose with the rancher-server and RAP should be, so I can reach the rancher-server on my domain, before I create the agent.
Any ideas on how I should tackle this? =/
Thank you a lot for your hard work!
The text was updated successfully, but these errors were encountered: