-
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
Control Plane Fails to Start on Fedora 35 with rootless podman #2524
Comments
Logs from control-plane node:
|
:/ |
PR: #2525 |
@BenTheElder was right, we have some logic kind/pkg/cluster/internal/providers/podman/util.go Lines 119 to 133 in b6bc112
but seems podman output has changed :/
|
it didn't change in podman, we are not using the same logic we use in docker, I have a PR for fixing that #2527 @rverenich any chance you can try with the PR I linked and confirm if this works? I don't have a system handy for testing the patch |
/etc/containers/storage.conf
/etc/containers/storage.conf
|
I mean if you can checkout #2527, |
of course kind version 0.12.0-alpha+09b2bcb0f7ebcb output from driver = "overlay"
driver = "btrfs"
|
it seems the errors are the same
@mheon does this rings a bell? any suggestion? |
@aojea the better way to test this is a kind config that unconditionally extraMounts /dev/mapper and see if that helps, completely cutting out the detection logic (which we can then spend time getting correct if the end result is helpful to begin with). |
diff --git a/pkg/cluster/internal/providers/podman/util.go b/pkg/cluster/internal/providers/podman/util.go
index 393f6ada..606f2ccb 100644
--- a/pkg/cluster/internal/providers/podman/util.go
+++ b/pkg/cluster/internal/providers/podman/util.go
@@ -119,6 +119,7 @@ func deleteVolumes(names []string) error {
// mountDevMapper checks if the podman storage driver is Btrfs or ZFS
func mountDevMapper() bool {
+ return true
cmd := exec.Command("podman", "info", "--format", "json")
out, err := exec.Output(cmd)
if err != nil { |
No code changes necessary: kind: Cluster
apiVersion: kind.x-k8s.io/v1alpha4
nodes:
- extraMounts:
- hostPath: /dev/mapper
containerPath: /dev/mapper
or in a shell: cat << EOF | kind create cluster --config=-
kind: Cluster
apiVersion: kind.x-k8s.io/v1alpha4
nodes:
- extraMounts:
- hostPath: /dev/mapper
containerPath: /dev/mapper
EOF |
with config.yaml provided driver = "overlay"
driver = "btrfs"
|
Ok then
with driver = "btrfs"
and finally started |
ok, then this seems a dup of #2411 (comment) is there any way to automate this? |
#2411 (comment) currently we don't know of one (otherwise we'd have implemented it). podman/docker don't expose these. we'd have to do something gross, slow, and API breaking like running a container that mounts I recommend using a filesystem with better support from Kubernetes, kubernetes has also failed to work properly on these filesystems in the past and has no CI on them. CI is ext4 + overlayfs (and maybe some fuse-overlayfs). |
This does seem to be a dupe #2524 (comment) |
What happened:
When using the podman provider, the KinD control plane fails to come up on Fedora 35
What you expected to happen:
Control plane to start using rootless Podman
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
configured to comply https://kind.sigs.k8s.io/docs/user/known-issues/#fedora
https://kind.sigs.k8s.io/docs/user/rootless/
tried both drivers in /etc/containers/storage.conf
Environment:
kind version
):kind v0.11.1 go1.16.8 linux/amd64
kind v0.12.0-alpha go1.16.8 linux/amd64
kubectl version
):N/A
docker info
):/etc/os-release
):The text was updated successfully, but these errors were encountered: