-
-
Notifications
You must be signed in to change notification settings - Fork 466
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
Load balancer is waiting for logs that already exist. #592
Comments
Hi @ybettan , thanks for opening this issue! On a side-note: which cgroup version is your system running? Seems like it's not shown in the docker info 🤔 |
Thank you for your answer @iwilltry42 If you are talking about the docker demon, then yes, it is running:
I don't think this is the case here.
I am SSHing to that entire machine,
After following https://unix.stackexchange.com/questions/471476/how-do-i-check-cgroup-v2-is-installed-on-my-machine, seems like I have V2. Maybe some extra info will help, when I reboot the machine, usually, the first try to install the cluster works BUT the |
I actually meant the containers, which you can check via
Then you would need to run |
Yes, it runs and the logs exist.
That didn't work, same issue, first installation works but |
Can you please paste them here or in a Gist/pastebin? |
DNS issue? |
Yeah, it does look like some networking issue on your end there 🤔 |
I believe I do, I am running RHEL8 on provisioned VMs at RedHat. Thank you for your support. |
Hey @ybettan , do you have any update on this issue? 👍 |
Hey @iwilltry42 , I didn't really have the time to continue investigating it. It works on my mac but doesn't on the Linux server I am using for work so I keep using minikube until I can find some time to debug it. Also, I have seen that multiple issues have been opened mentioning this one so I have assumes there is a real bug here. |
So I created a debug release to at least try to get a clue about what's happening here. This should generate logs where the loadbalancer logs are included in the output to ensure that there's no clock skew involved (though, to be save, I also dropped subsecond precision from the wait command). |
What did you do
How was the cluster created?
k3d cluster create --trace
What did you do afterwards?
Nothing
What did you expect to happen
k3d command to finish without error.
Screenshots or terminal output
Which OS & Architecture
Which version of
k3d
Which version of docker
Seems like k3d wait for logs that already exist:
The text was updated successfully, but these errors were encountered: