Skip to content
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

Exiting due to K8S_INSTALL_FAILED: Failed to update cluster #17446

Closed
Tracked by #17447
aungzanbaw opened this issue Oct 19, 2023 · 5 comments
Closed
Tracked by #17447

Exiting due to K8S_INSTALL_FAILED: Failed to update cluster #17446

aungzanbaw opened this issue Oct 19, 2023 · 5 comments

Comments

@aungzanbaw
Copy link

What Happened?

minikube start --driver=docker --container-runtime=containerd
😄 minikube v1.31.2 on Debian 11.8 (amd64)
✨ Using the docker driver based on existing profile
❗ docker is currently using the btrfs storage driver, setting preload=false
👍 Starting control plane node minikube in cluster minikube
🚜 Pulling base image ...
🏃 Updating the running docker "minikube" container ...
📦 Preparing Kubernetes v1.27.4 on containerd 1.6.21 ...
▪ kubelet.localStorageCapacityIsolation=false
❌ Unable to load cached images: loading cached images: containerd load /var/lib/minikube/images/kube-scheduler_v1.27.4: ctr images import: sudo ctr -n=k8s.io images import /var/lib/minikube/images/kube-scheduler_v1.27.4: Process exited with status 1
stdout:
unpacking registry.k8s.io/kube-scheduler:v1.27.4 (sha256:8f9366ba8bf01624e82d747591842a2a0b24f5e94bdc3f96f92904df10b02a9b)...
stderr:
time="2023-10-19T02:24:07Z" level=info msg="apply failure, attempting cleanup" error="failed to extract layer sha256:6fbdf253bbc2490dcfede5bdb58ca0db63ee8aff565f6ea9f918f3bce9e2d5aa: failed to mount /var/lib/containerd/tmpmounts/containerd-mount1939106962: invalid argument: unknown" key="extract-631255805-pXSV sha256:9300705518a3ff9222e78cbbabf1108e0b3336c28a1d40b05cfea89bc41d1bd0"
ctr: failed to extract layer sha256:6fbdf253bbc2490dcfede5bdb58ca0db63ee8aff565f6ea9f918f3bce9e2d5aa: failed to mount /var/lib/containerd/tmpmounts/containerd-mount1939106962: invalid argument: unknown

> kubelet.sha256:  64 B / 64 B [-------------------------] 100.00% ? p/s 0s
> kubectl.sha256:  64 B / 64 B [-------------------------] 100.00% ? p/s 0s
> kubeadm.sha256:  64 B / 64 B [-------------------------] 100.00% ? p/s 0s
> kubelet:  6.45 MiB / 101.25 MiB [>______________] 6.37% 828 B p/s 2h16m7s
> kubectl:  7.24 MiB / 46.98 MiB [-->____________] 15.42% 930 B p/s 2h16m7s
> kubeadm:  8.57 MiB / 45.93 MiB [-->_________] 18.67% 1.08 KiB p/s 2h16m6s

❌ Exiting due to K8S_INSTALL_FAILED: Failed to update cluster: updating control plane: downloading binaries: downloading kubelet: download failed: https://dl.k8s.io/release/v1.27.4/bin/linux/amd64/kubelet?checksum=file:https://dl.k8s.io/release/v1.27.4/bin/linux/amd64/kubelet.sha256: getter: &{Ctx:context.Background Src:https://dl.k8s.io/release/v1.27.4/bin/linux/amd64/kubelet?checksum=file:https://dl.k8s.io/release/v1.27.4/bin/linux/amd64/kubelet.sha256 Dst:/home/aungzanbaw/.minikube/cache/linux/amd64/v1.27.4/kubelet.download Pwd: Mode:2 Umask:---------- Detectors:[0x3f9c8a8 0x3f9c8a8 0x3f9c8a8 0x3f9c8a8 0x3f9c8a8 0x3f9c8a8 0x3f9c8a8] Decompressors:map[bz2:0xc0001f49a8 gz:0xc0001f4a00 tar:0xc0001f49b0 tar.bz2:0xc0001f49c0 tar.gz:0xc0001f49d0 tar.xz:0xc0001f49e0 tar.zst:0xc0001f49f0 tbz2:0xc0001f49c0 tgz:0xc0001f49d0 txz:0xc0001f49e0 tzst:0xc0001f49f0 xz:0xc0001f4a08 zip:0xc0001f4a20 zst:0xc0001f4a30] Getters:map[file:0xc001480810 http:0xc000d68eb0 https:0xc000d68f00] Dir:false ProgressListener:0x3f579a0 Insecure:false DisableSymlinks:false Options:[0x12d0880]}: read tcp [240b:11:b100:d400:216:3eff:fe0c:d4b5]:34184->[2a04:4e42:1a::311]:443: read: network is unreachable

╭───────────────────────────────────────────────────────────────────────────────────────────╮
│ │
│ 😿 If the above advice does not help, please let us know: │
│ 👉 https://github.com/kubernetes/minikube/issues/new/choose
│ │
│ Please run minikube logs --file=logs.txt and attach logs.txt to the GitHub issue. │
│ │

Attach the log file

Could´t download nor start the minikube.

Linux penguin 5.15.130-20470-g75de2d59bd35 #1 SMP PREEMPT Fri Oct 13 18:29:56 PDT 2023 x86_64 GNU/Linux

amd64

Distributor ID: Debian
Description: Debian GNU/Linux 11 (bullseye)
Release: 11
Codename: bullseye

Operating System

Other

Driver

Docker

@aungzanbaw
Copy link
Author

docker run gcr.io/k8s-minikube/kicbase:v0.0.40

  • userns=
  • grep -Eqv '0[[:space:]]+0[[:space:]]+4294967295' /proc/self/uid_map
  • userns=1
  • echo 'INFO: running in a user namespace (experimental)'
    INFO: running in a user namespace (experimental)
  • validate_userns
  • [[ -z 1 ]]
  • local nofile_hard
    ++ ulimit -Hn
  • nofile_hard=1048576
  • local nofile_hard_expected=64000
  • [[ 1048576 -lt 64000 ]]
  • [[ -f /sys/fs/cgroup/cgroup.controllers ]]
  • configure_containerd
  • local snapshotter=
  • [[ -n 1 ]]
  • sed -i 's/restrict_oom_score_adj = false/restrict_oom_score_adj = true/' /etc/containerd/config.toml
  • [[ -z '' ]]
  • overlayfs_preferrable
  • [[ -z 1 ]]
  • [[ -e /sys/module/overlay/parameters/permit_mounts_in_userns ]]
    ++ mktemp -d
  • tmp=/tmp/tmp.vNwK7SXtym
  • mkdir -p /tmp/tmp.vNwK7SXtym/l /tmp/tmp.vNwK7SXtym/u /tmp/tmp.vNwK7SXtym/w /tmp/tmp.vNwK7SXtym/m
  • mount -t overlay -o lowerdir=/tmp/tmp.vNwK7SXtym/l,upperdir=/tmp/tmp.vNwK7SXtym/u,workdir=/tmp/tmp.vNwK7SXtym/w overlay /tmp/tmp.vNwK7SXtym/m
    mount: /tmp/tmp.vNwK7SXtym/m: permission denied.
    INFO: UserNS: kernel does not seem to support overlayfs.
  • echo 'INFO: UserNS: kernel does not seem to support overlayfs.'
  • rm -rf /tmp/tmp.vNwK7SXtym
    INFO: changing snapshotter from "overlayfs" to "fuse-overlayfs"
  • return 1
  • snapshotter=fuse-overlayfs
  • [[ -z fuse-overlayfs ]]
  • [[ -n fuse-overlayfs ]]
  • echo 'INFO: changing snapshotter from "overlayfs" to "fuse-overlayfs"'
  • sed -i 's/snapshotter = "overlayfs"/snapshotter = "fuse-overlayfs"/' /etc/containerd/config.toml
  • [[ fuse-overlayfs = \f\u\s\e-\o\v\e\r\l\a\y\f\s ]]
  • echo 'INFO: enabling containerd-fuse-overlayfs service'
    INFO: enabling containerd-fuse-overlayfs service
  • systemctl enable containerd-fuse-overlayfs
    Failed to enable unit, unit containerd-fuse-overlayfs.service does not exist.

@aungzanbaw
Copy link
Author

dmesg | grep module

[ 0.810332] RPC: Registered named UNIX socket transport module.
[ 0.813584] RPC: Registered udp transport module.
[ 0.816164] RPC: Registered tcp transport module.
[ 0.819062] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 1.125690] kvm: already loaded the other module
[ 1.613005] loop: module loaded

@aungzanbaw
Copy link
Author

lscpu | grep Virtualization
Virtualization: VT-x
Virtualization type: full

@aungzanbaw
Copy link
Author

uname -r
5.15.130-20470-g75de2d59bd35

@aungzanbaw
Copy link
Author

"Overlayfs kernel module to be enabled on ChromeOS" and duplicate with #10431 #6411 #763

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant