Following Tutorial In Readme.md #99
Comments
|
Hey Julian, when the metal-core does not come up it is likely that it cannot reach the metal-api in the kind cluster. You can enter the leaf switch using Just a small assumption: I can imagine that sometimes name resolution on |
|
The error with |
|
Under some circumstances systemd-resolved does not resolv |
|
Hi @Gerrit91 and hi @majst01, Is there another network interface I have to configure to solve this problem? |
|
@JulianHBuecher |
|
Hi @GrigoriyMikhalkin |
|
On my machine it looks like: The gateway address has to be 172.17.0.1 such that they can communicate with the Kind cluster (which is a known limitation of the lab and is briefly mentioned in the requirements section). |
|
Hi Gerrit, The first leaf: And the second: After checking the network list from docker, I assume the run both in the same network: EDIT: |
|
Thanks for looking it up. Looks good to me. I guess, then we'll need to inspect the other end of the line. Are there any other error logs during the provisioning with Ansible? You can use |
|
Hi @Gerrit91, So, I evaluated the cluster and the API. Here are the following outputs: ... and executing the curl: ... I couldn't believe it. Is it possibly a problem the metal-console is not reachable by the ingress? Or is this the next activation step in the flow? |
|
Okay, so your control plane also looks fine. Running a bit out of options, but I am pretty sure we'll find it, so thanks for hanging in. 👍 The metal-console is just an optional component that does not function for the mini-lab because it requires a BMC for accessing a machine's serial console. The service should not be added to the ingress config, but it shouldn't harm either. I created a pull request in order to clean this up: #100. Can you also reach the metal-api from a leaf switch? Also the following request (failing endpoint from your metal-core logs) should return a response: I hope that the docker-compose version does not cause any issues. I am running on v2.1.1, where I think they did a complete re-write from Python to Golang. I remember I had to make small changes to this project when docker-compose v2 was introduced. |
|
Hi @Gerrit91, So I've updated my Docker-Compose Installation to Version v2.3.3 and tried it again. For our sake with no effect (updated the files from |
|
Hi Julian, out of curiosity, do you have a Mac ? |
|
It's indeed suspicious that reaching the host system through the Docker Gateway does not work as I think it's not so uncommon to do on a Linux machine for development purposes. On other operating systems this trick will not work (see here for Docker on Mac). |
|
Hi @majst01, and Hi @Gerrit91, I did not get it either... Are you running the lab on your local machine or inside a VM? Maybe I should try it on a fresh installation inside VirtualBox or so |
|
Hi, I am running it on the local machine. VM is probably tough as it would require nested virtualization, which can quickly make things more complicated than expected. Still have to think about why you cannot reach your host system through the Docker bridge. It would be interesting to see if it works for you with a minimal example. Something like: |
|
Hi @Gerrit91, To get access to the host network through the docker bridge I have to use the following command: julian@Julian-XPS-15:~$ docker run --rm -it --network host alpine wget -O- 172.17.0.1:5000
Connecting to 172.17.0.1:5000 (172.17.0.1:5000)
writing to stdout
<!DOCTYPE html>
<html>
<head>
<title>Welcome to nginx!</title>
<style>
html { color-scheme: light dark; }
body { width: 35em; margin: 0 auto;
font-family: Tahoma, Verdana, Arial, sans-serif; }
</style>
</head>
<body>
<h1>Welcome to nginx!</h1>
<p>If you see this page, the nginx web server is successfully installed andOtherwise, the command hangs in host resolution: The direct call via the bridge network works fine... Additionally I did a little bit of research and found an interesting StackOverflow article mentioning this kind of problematic. For reference see here https://stackoverflow.com/questions/31324981/how-to-access-host-port-from-docker-container Edit: |
|
Running the leaf switches in host network will not work. There is a lot of network things going on that you definitely do not want on your host system. In the stackoverflow issue you posted there is one suggestion regarding iptables. Have you tried this already? |
|
Hi @Gerrit91, I have to apologise for all that hustle... next time I think twice before reaching out to you again... But now I could test it for my project. Thank you very much for your help guys. Really appreciate that. |
|
You don't have to apologize. I am really happy that you want to try it out and shared the problem. Maybe it helps someone else, too. You are also invited to our metal-stack Slack channel when you have smaller questions. |
Specs
Problem
Hi,
today I tried the tutorial found in the README.md. After several cleanups and restarts I did not get it to work. Every time creating the metal-core I got the following error:
The error tells me, the host does not support a requested feature. I have found similar issues in other virtualization software like podman (see containers/podman#11479).
Is there something I missed during configuration of my machine or software?
Hopefully you could help me out here.
Best regards Julian
The text was updated successfully, but these errors were encountered: