Replies: 8 comments 12 replies
-
|
Check the containerd log file at |
Beta Was this translation helpful? Give feedback.
-
|
the containerd.log file doesnt exist .. i can reach the path to /var/lib/rancher/rke2/agent/containerd/ but no files in it. |
Beta Was this translation helpful? Give feedback.
-
|
Take in consideration that if i try to install k3s it works .. but rke2 is not starting. |
Beta Was this translation helpful? Give feedback.
-
|
if i run rke2 server --debug i get the following logs which has more details: |
Beta Was this translation helpful? Give feedback.
-
There should be MANY more files in this list. It appears that it's hung extracting the binaries from the runtime image - it hasn't even finished with containerd yet, let alone the kubelet or other critical files. What files do you see under |
Beta Was this translation helpful? Give feedback.
-
|
I tried deleting the data folder and restarting .. its the same output below: Here is the path content: user@monitara-kuber01:/var/lib/rancher/rke2$ cd data
user@monitara-kuber01:/var/lib/rancher/rke2/data$ dir
v1.24.9-rke2r1-d4d8faf800d0
user@monitara-kuber01:/var/lib/rancher/rke2/data$ cd v1.24.9-rke2r1-d4d8faf800d0
user@monitara-kuber01:/var/lib/rancher/rke2/data/v1.24.9-rke2r1-d4d8faf800d0$ dir
bin
user@monitara-kuber01:/var/lib/rancher/rke2/data/v1.24.9-rke2r1-d4d8faf800d0$ cd bin
user@monitara-kuber01:/var/lib/rancher/rke2/data/v1.24.9-rke2r1-d4d8faf800d0/bin$ dir
containerd
user@monitara-kuber01:/var/lib/rancher/rke2/data/v1.24.9-rke2r1-d4d8faf800d0/bin$ |
Beta Was this translation helpful? Give feedback.
-
|
hmm, you got even less that time. I can't say I've seen this before. Are you using the airgap tarballs, or a private registry mirror, or just pulling directly from Docker Hub? Do you have any security agents or proxies in place that might be interfering with things? This looks like something uniquely broken in your environment. |
Beta Was this translation helpful? Give feedback.
-
|
I am following the Quick Start guide .. it seems etcd is not starting and issues are propagating afterwards .. this is the first error as I see when I run rke2 server --debug: INFO[0000] Tunnel server egress proxy waiting for runtime core to become available |
Beta Was this translation helpful? Give feedback.
-
|
Nothing else is going to work until the rest of the files in the rke2-runtime image are extracted out to disk, and containerd and the kubelet are executed. For some reason, it is hanging partway through extracting out the image contents to disk. If you're confident that there are not any agents/proxies/firewalls that would interfere with the download, I would check the network on this host to confirm that it is configured correctly and isn't dropping out partway through the image pull. |
Beta Was this translation helpful? Give feedback.
-
|
Hi Brandon, |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
No, that is the correct content for those files. Those are not URLs, those are image references. hub.docker.com is the web interface for browsing the images stored on index.docker.io. This is not the source of your problem. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @brandond .. running rke2 --debug shows looking into the folder /var/lib/rancher/rke2/agent/images below is the list of files: |
Beta Was this translation helpful? Give feedback.
-
|
BTW .. I tried to install with a specific version of rke2 but it always tries to install v1.24.9+rke2r1 .. no matter what version I specify .. I wanted to try out the latest version which I think is v1.26.0+rke21 |
Beta Was this translation helpful? Give feedback.
-
|
Those mesasges indicate that it's pulling the image from a remote registry because it can't find any local tarballs. Did you attempt to provide it with any? This would be covered in the airgap install docs, if you are attempting to run airgapped. It sounds like you're not requesting the version properly. How are you attempting to do so? |
Beta Was this translation helpful? Give feedback.
-
|
Hi @brandond .. I managed to make the server node run .. where its service in systemctl is active and running .. using the following command: But now i am having another issue .. sudo kubectl get nodes doesnt work and gives the following error: |
Beta Was this translation helpful? Give feedback.
-
|
That means it's not started yet and hasn't created a kubeconfig file at /etc/rancher/rke2/rke2.yaml - or you've not pointed kubectl at that config file by setting the KUBECONFIG environment variable. |
Beta Was this translation helpful? Give feedback.
-
|
Same for Ubuntu 24.04. @SamerX , I think you can update the bugreport title. |
Beta Was this translation helpful? Give feedback.
-
|
All the CI for RKE2 runs on Ubuntu, both 22.04 and 24.04, and it does work. There is likely something wrong with your setup. |
Beta Was this translation helpful? Give feedback.
-
|
For some reason it was thinking Hope this helps |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I am trying to get rke2 installed on Ubuntu 20.04 or 22.04, the failure happens when I attempt to start the rke2 service, it gives the following error:
I figured out that the /run/k3s/containerd/containerd.sock is not being installed at all .. am I missing something as pre-requirement?
Beta Was this translation helpful? Give feedback.
All reactions