-
-
Notifications
You must be signed in to change notification settings - Fork 275
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
CI Currently broken - kubelet won't start in GitHub Actions #125
Comments
New issue: need to upgrade config:
|
Now getting errors on image pull...
|
I set
|
Had to add a couple options for running inside a container: kubernetes/kubernetes#43704
And then also merged in work from #107 and it is passing locally. Running it through CI now. |
Hmm... now on Debian 11 only, on GitHub Actions, I'm getting:
That's just a warning though... maybe not a fatal issue with the install. It seems to run just fine locally... |
Full error log:
|
And output of
And
|
Hmm... getting this on Rocky Linux 8, too:
|
On my Mac, I'm seeing:
I already have the volume mount |
Maybe need to add ...but I wonder what version of Docker is running on Ubuntu in the GitHub Actions environments... |
@geerlingguy I have tested this role in debian and Ubuntu vm's and got same issue. Looks like the error is related to this issue. |
@sasidatta - It seems like the Calico problem was fixed with some of the changes in my PR (#126), but it's not working for some other reasons now. |
I noticed I was still using
|
Switching to use |
Now getting:
And it looks like it's having issues with the |
Meh, having some other issues now, it seems like containers just aren't getting started. |
Not quite fixed, I just merged all the work in that PR since it's still useful for SOOO many different things (e.g. see #132 as well...). |
Running the kubelet init task with elevated privileges gets me past the errors, but everything is increadibly unstable. The cluster never leaves the 'NotReady' stage and crashes completely after a few minutes. Kubelet, Docker and containerd services are running and seem to be healthy. Using Ubuntu 22 on a single node cluster. Don't quite know how to debug this further. |
See:
Running locally, I'm hitting:
But I'm pretty sure that's because I'm testing under aarch64:
And I'm not sure if the
jammy
repo has ARM64 packages available. Trying to force AMD64 now...The text was updated successfully, but these errors were encountered: