-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Starting kind cluster with Podman fails #1735
Comments
possibly https://kind.sigs.k8s.io/docs/user/known-issues/#fedora32-firewalld, though that's only known for sure with docker. |
oh also podman 2 + requires a fix in some cases anyhow due to a podman change #1734, what commit do you have installed? ( |
Previously to me running |
Ah the issue is probably because I am using |
oh yes, we're not quite there yet, Kubernetes and KIND are getting patches
related to this.
#1727 will support cgroupsv2
_docker_ / rootless once some patches land in kubernetes, but podman still
needs other changes.
…On Thu, Jul 16, 2020 at 11:43 AM Andrew Stoycos ***@***.***> wrote:
Ah the issue is probably because I am using cgroupsV2, I will try to
revert back now
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#1735 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAHADK7YR6ZWIS7PRJN7Z2DR35C47ANCNFSM4O4WU5CQ>
.
|
yes that is definitely not working. Unless you use kubernetes git master, that is fine with cgroups v2. I've tested it a couple of days ago with kinD and Podman on Fedora 32 and cgroup v2. Rootless is going to take a while, I need to get CNI working inside of the rootless environment |
Awesome, thank you!! 😀
…On Thu, Jul 16, 2020, 13:29 Giuseppe Scrivano ***@***.***> wrote:
Ah the issue is probably because I am using cgroupsV2, I will try to
revert back now
yes that is definitely not working. Unless you use kubernetes git master,
that is fine with cgroups v2. I've tested it a couple of days ago with kinD
and Podman on Fedora 32 and cgroup v2. Rootless is going to take a while, I
need to get CNI working inside of the rootless environment
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#1735 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAHADK55OLCW3ZOZ2ZHL7X3R35PKTANCNFSM4O4WU5CQ>
.
|
Yep I was seeing the same thing :), I've reverted back to cgroupsv1 and it seems to be alright now Thanks! |
Great!
…On Thu, Jul 16, 2020 at 2:39 PM Andrew Stoycos ***@***.***> wrote:
Yep I was seeing the same thing :), I've reverted back to cgroupsv1 and it
seems to be alright now Thanks!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#1735 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAHADK73ROWSMCWXPVLN7EDR35XRFANCNFSM4O4WU5CQ>
.
|
What happened
Running
kind create cluster
on Fedora 32 with podman fails with the following errorWhat you expected to happen:
The cluster to spin up normally
How to reproduce it (as minimally and precisely as possible):
Download kind from master with
go get sigs.k8s.io/kind@master
enter root user space with
sudo su -
run
kind create cluster
Anything else we need to know?:
Trying to run
sudo kind create cluster
does not work, I have to enter the root space withsudo su -
before running any kind commandsEnvironment:
Fedora 32
kind version
):kind v0.9.0-alpha go1.14.3 linux/amd64
kubectl version
):Using Kubernetes version: v1.18.2
docker info
):Podman version 2.0.2
/etc/os-release
): FedoraThe text was updated successfully, but these errors were encountered: