-
Notifications
You must be signed in to change notification settings - Fork 385
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
Using k0s in Podman on Fedora 34 Silverblue #1195
Comments
Have you joined any worker? by default the controller node starts with no workers. Please follow the instruction here https://docs.k0sproject.io/v1.22.2+k0s.1/k0s-in-docker/#2-optional-create-additional-workers |
No, I saw it was optional and figured that k0s would untaint the control plane or master node. Here is the output with me following the optional steps. ➜ ~ podman run -d --name k0s --hostname k0s --privileged -v /var/lib/k0s -p 6443:6443 docker.io/k0sproject/k0s:latest
3151eef3f342342e5fb49bebd3429a28ca1748d622a7423b4ef1549cae5ee6fc
➜ ~ token=$(podman exec -t -i k0s k0s token create --role=worker)
➜ ~ echo $token
H4sIAAAAAAAC/2yV3Y6jMBKF7/sp8gI9Y0PT2o60F0OCSUjjjG3KTnwHmAlgk9CEzg+rffdVZ2akXWnvylVH37Esq85T3jeyGs7N6TifXfBT6T7PYzWc50/Psz/1/Gk2m83O1XCphvmsHsf+PP/+HaNv6Jv3DSM0f3158R+ashrG5ldT5mP1nH+O9Wloxvuzycd8PnsXaHwXeMHBJFkTLrlMQIBOGCLAHzM0LixOBPCQR3TJlOw1Ir6AJNTISQ5kK6LbmYIcWVvTbfwWq86t9kimEDFPkJobxLmC/r3AfZKvdJtZwjlcN8yR0CATcWkoc2TFMvLFe8kgqFOse+XqjZH9HrpbW2XkQ0keatB+unJURtLPJB+qCL+yLKE8Smp+LK/Vof87a/97lkFyrCL9waRcaBQoZgmVEd+ZJdGF1MG+wyol/T7bcZ1a6WvPkBxwmEZmCT5ZLRxN9i2NAOSCSSIZREhAEhlEHlqByOXrTQD4UlmdyJasZEfGFPM1s4TLWF9oR4IsxgH18DY//kAmKjc5DlvRgZ+BOYNH8btvXvPFmBY755ldwvIju5p4fReW5AzrU25HVMTyzNr1NVXkso2CRelgSAFvTMc/ypivc9YnHBK6XYy5xsaXxAzZivrZ6nBlbXjKl7KW8eGFo/G03fEUIudl3puTzlnwbmvp16/bHXlX4Ia9JKPZ9a5cus3CuauOA8Em4pdeshEreoVlqIrpB2Y7edbOiLJ1i3QKSeH1fdqNY7o0J01kapA+KtCB6sxlu+M13/Uxy9Z3mNhG3McIZOoVXt2b6QemCF3zzn3A0ghjgyZH+MJ28q69cbO3QSNkeku75JK2LsxduCl9uoGo7jYezzLvfNf2NHDWn5ki2zyuJ+GTm+7e+gpqJSaZlllIoaOatgbnLRG6TadU6S2f6nth6ybzRrSFNwFZ6TNlKLMk5F7Pc5uEC4tDGpkwldLylSGsefMBZGiQW7CuDyFKjpnTa7B4wdT+hUMCDHgIcLhksL5yFN2k4pHGZMdsAkAOw17ajdyll3yqsXJ1QG2KUzTu9VK+aJ+SypIt68xQqnrIoQzMFH79wYlbEmaIhl/+ue/SjCTbqgt6swxPVdQrYP1WT6TTyrzKrrewSzJ2lELb/qeWYZNZt1MrfhfHPd5bfBUEvGKVMGHpTw3rgMauVrsfV+olnBMZCcV86AAvupvk6ISLuN4WLdVUridj8TsD7fF4/Fk2/wiEpT34Fhc7GXKVBgKTzzzqX4qlnja+xHuP7tkkRxG/XLbqzUqENmBtUJDkBEvHZWv6MnaxAUmEO+C9tXfaBXfuYRDLEmdLFzFvfC/AJTrjH7yzF6puLo/Wk+zqZo9Il07Uh2sfliuH8kl/SEffS3urjTVnEUd+KvXA7uNVkjIQET7BsvZFfBgy1+8B871UfS+Osi1cPRXRW6KaURVZGahMbhbNGRsnAaLDTSzrJIPDLW1GyxTdatKjtDNrFZFIZ+kVkB7Zbh0Ym/DMHoZcOSehvxu1DoosQqUNrGzehCGwSRUhqev5zwxt/uxmkll2YEgKGblYAA1lBI+9/M5O/3yazY55V81nFp2fytNxrG7j75T4Xf9Oib+R8VB9NT7Pj9NnUblqfC5Op/E8Dnn/v7TPYaiO4/Nf0qNpm6OZzxan46/m8NQP1a9qqI5ldZ7P/vXvpy/qw/wP5P/gH8aPK4wnWx3nM3Ns8+DlW3upPtpD+3E4t5V/wB9P/wkAAP//B5DgyQIHAAA=
➜ ~ podman run -d --name k0s-worker1 --hostname k0s-worker1 --privileged -v /var/lib/k0s docker.io/k0sproject/k0s:latest k0s worker $token
b14cf0ae2031eb25830090290a46adfb5d655630ffdab615b4c42f232312e5ba
➜ ~ podman exec k0s kubectl get nodes
No resources found
➜ ~ Logs, too large for comments |
@FilBot3 oh yeah, you are absolutely right, I forgot that docker image for k0s by default enables worker for the controller node by using I haven't been using podman that much, based on the logs there is some issue with volume for the
Need to check in details how podman works with volumes |
@Soider what would you like me to do to help out more? |
Looks like it's related to cgroups v2, there is a similar issue in k3s/k3d: k3d-io/k3d#493 |
@FilBot3 By default, podman is running in a rootless mode that we currently don't support. Try running it with |
Am using rhel 8 and can i check if we need to do anything to use podman instead of containerd? or it works out of the box? |
@lchunleo This specific issue is about running k0s in Podman, as an alternative to Docker. If I understand your question correctly, you want k0s to use Podman as a container runtime via CRI, instead of the bundled containerd? I doubt that's possible. As far as I know, Podman doesn't even implement the Container Runtime Interface. Do you have any a reference for it? If so, feel free to file a new issue or reach out on the forums. |
The issue or request
I am trying to run k0s in Podman on Fedora 34 Silverblue in an attempt to see if it would even work. I copied and pasted commands 1 and 3 because 2 was optional from the k0s in Docker docs page. The Control Plane seems to come up, but isn't showing any resources. It seems to be in a continual crash and restart loop. Has anyone else tried this or had luck with it?
The details
Version
Platform
Which platform did you run k0s on?
What happened?
A clear and concise description of what the bug is.
When using Podman to run a single node k0s instance, the kubectl get nodes command returns no resources found.
How To Reproduce
How can we reproduce this issue? (as minimally and as precisely as possible)
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots & Logs
If applicable, add screenshots to help explain your problem.
Also add any output from kubectl if applicable:
I expected to see a table output of at least a single node which is performing the control plane and kubelet function.
Additional context
Add any other context about the problem here.
Podman logs of k0s
The text was updated successfully, but these errors were encountered: