Control Plane Fails to Start on Fedora 34 Silverblue #2521
Comments
|
I see fuse-overlayfs, is this rootless podman? https://kind.sigs.k8s.io/docs/user/rootless/ |
|
can you run with |
This is rootless podman, and I believe I configured the
I have posted them at the gist here - https://gist.github.com/adambkaplan/13e99a24c4d1f98475739a672a7ae019 |
|
Also added results of the systemctl hints from the main container process to the gist. |
BenTheElder
added
area/provider/podman
|
I think we've had some other recent issues with fuse-overlayfs |
|
I would try kind from master first, this was merged recently |
|
If it helps in any way, i am possibly experiencing the same issue as the OP on fedora 34 ( also with podman and rootless ). Let me know if i can help with debugging in any way. |
@mrWinston you are hitting this problem #2411 , that is not really something KIND can fix :/ |
|
@aojea oh, yes. you're right, applying the workaround from the linked issue does indeed solve it for me. Thanks for the quick reply! |
|
This worked for me given this configuration (Fedora 35 with rootless Podman): $ cat /etc/os-release
NAME="Fedora Linux"
VERSION="35 (Workstation Edition)"
ID=fedora
VERSION_ID=35
VERSION_CODENAME=""
PLATFORM_ID="platform:f35"
PRETTY_NAME="Fedora Linux 35 (Workstation Edition)"
ANSI_COLOR="0;38;2;60;110;180"
LOGO=fedora-logo-icon
CPE_NAME="cpe:/o:fedoraproject:fedora:35"
HOME_URL="https://fedoraproject.org/"
DOCUMENTATION_URL="https://docs.fedoraproject.org/en-US/fedora/f35/system-administrators-guide/"
SUPPORT_URL="https://ask.fedoraproject.org/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_BUGZILLA_PRODUCT="Fedora"
REDHAT_BUGZILLA_PRODUCT_VERSION=35
REDHAT_SUPPORT_PRODUCT="Fedora"
REDHAT_SUPPORT_PRODUCT_VERSION=35
PRIVACY_POLICY_URL="https://fedoraproject.org/wiki/Legal:PrivacyPolicy"
VARIANT="Workstation Edition"
VARIANT_ID=workstation
$ podman version
Version: 3.4.4
API Version: 3.4.4
Go Version: go1.16.8
Built: Wed Dec 8 22:45:07 2021
OS/Arch: linux/amd64
$ podman info
host:
arch: amd64
buildahVersion: 1.23.1
cgroupControllers:
- memory
- pids
cgroupManager: systemd
cgroupVersion: v2
conmon:
package: conmon-2.1.0-2.fc35.x86_64
path: /usr/bin/conmon
version: 'conmon version 2.1.0, commit: '
cpus: 32
distribution:
distribution: fedora
variant: workstation
version: "35"
eventLogger: journald
hostname: mbana-pc3
idMappings:
gidmap:
- container_id: 0
host_id: 1000
size: 1
- container_id: 1
host_id: 100000
size: 65536
uidmap:
- container_id: 0
host_id: 1000
size: 1
- container_id: 1
host_id: 100000
size: 65536
kernel: 5.16.7-200.fc35.x86_64
linkmode: dynamic
logDriver: journald
memFree: 40270614528
memTotal: 67404099584
ociRuntime:
name: crun
package: crun-1.4.2-1.fc35.x86_64
path: /usr/bin/crun
version: |-
crun version 1.4.2
commit: f6fbc8f840df1a414f31a60953ae514fa497c748
spec: 1.0.0
+SYSTEMD +SELINUX +APPARMOR +CAP +SECCOMP +EBPF +CRIU +YAJL
os: linux
remoteSocket:
path: /run/user/1000/podman/podman.sock
security:
apparmorEnabled: false
capabilities: CAP_CHOWN,CAP_DAC_OVERRIDE,CAP_FOWNER,CAP_FSETID,CAP_KILL,CAP_NET_BIND_SERVICE,CAP_SETFCAP,CAP_SETGID,CAP_SETPCAP,CAP_SETUID,CAP_SYS_CHROOT
rootless: true
seccompEnabled: true
seccompProfilePath: /usr/share/containers/seccomp.json
selinuxEnabled: true
serviceIsRemote: false
slirp4netns:
executable: /usr/bin/slirp4netns
package: slirp4netns-1.1.12-2.fc35.x86_64
version: |-
slirp4netns version 1.1.12
commit: 7a104a101aa3278a2152351a082a6df71f57c9a3
libslirp: 4.6.1
SLIRP_CONFIG_VERSION_MAX: 3
libseccomp: 2.5.3
swapFree: 8589930496
swapTotal: 8589930496
uptime: 8h 14m 58.74s (Approximately 0.33 days)
plugins:
log:
- k8s-file
- none
- journald
network:
- bridge
- macvlan
volume:
- local
registries:
search:
- docker.io
store:
configFile: /home/mbana/.config/containers/storage.conf
containerStore:
number: 1
paused: 0
running: 1
stopped: 0
graphDriverName: btrfs
graphOptions: {}
graphRoot: /home/mbana/.local/share/containers/storage
graphStatus:
Build Version: 'Btrfs v5.15.1 '
Library Version: "102"
imageStore:
number: 2
runRoot: /run/user/1000/containers
volumePath: /home/mbana/.local/share/containers/storage/volumes
version:
APIVersion: 3.4.4
Built: 1638999907
BuiltTime: Wed Dec 8 22:45:07 2021
GitCommit: ""
GoVersion: go1.16.8
OsArch: linux/amd64
Version: 3.4.4
$ kind --version
kind version 0.11.1Then tee ~/.config/containers/storage.conf <<'EOF'
[storage]
driver = "btrfs"
EOF
systemctl restart --now podman
podman system reset
tee config.yml <<'EOF'
kind: Cluster
apiVersion: kind.x-k8s.io/v1alpha4
nodes:
- extraMounts:
- hostPath: /dev/nvme0n1p1
containerPath: /dev/nvme0n1p1
EOFRun: kubectl cluster-info --context kind-test-1
Kubernetes control plane is running at https://127.0.0.1:41285
CoreDNS is running at https://127.0.0.1:41285/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy
To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'. |
|
Possibly #2584, certainly at least for this subthread #2521 (comment) |
|
This has gotten dated, we can revisit this with contemporary fedora/kind versions if there remain issues. |
|
Oh wow this was old. I can confirm that kind + rootless podman was working just fine on Fedora 37 Silverblue. |
What happened:
When using the podman provider, the KinD control plane fails to come up on Fedora 34 Silverblue.
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?:
Environment:
kind version):kind v0.11.0 go1.16.4 linux/amd64
kubectl version):N/A
docker info):/etc/os-release):The text was updated successfully, but these errors were encountered: