Skip to content

hostname: error while loading shared libraries: libc.so.6: cannot change memory protectionsย #21812

@learncloudevsecops

Description

@learncloudevsecops

What Happened?

logs.txt

Attach the log file

manohar@ThinkPad-E14-Gen-6:~/ElevateLabs/kubernetes-cluster-task5$ minikube start --driver=docker
๐Ÿ˜„ minikube v1.37.0 on Ubuntu 25.10
โœจ Using the docker driver based on existing profile
๐Ÿ‘ Starting "minikube" primary control-plane node in "minikube" cluster
๐Ÿšœ Pulling base image v0.0.48 ...
๐Ÿ”„ Restarting existing docker container for "minikube" ...
๐Ÿคฆ StartHost failed, but will try again: provision: ssh command error:
command : sudo hostname minikube && echo "minikube" | sudo tee /etc/hostname
err : Process exited with status 127
output : hostname: error while loading shared libraries: libc.so.6: cannot change memory protections

๐Ÿƒ Updating the running docker "minikube" container ...
๐Ÿ˜ฟ Failed to start docker container. Running "minikube delete" may fix it: provision: ssh command error:
command : sudo hostname minikube && echo "minikube" | sudo tee /etc/hostname
err : Process exited with status 127
output : hostname: error while loading shared libraries: libc.so.6: cannot change memory protections

โŒ Exiting due to GUEST_PROVISION: error provisioning guest: Failed to start host: provision: ssh command error:
command : sudo hostname minikube && echo "minikube" | sudo tee /etc/hostname
err : Process exited with status 127
output : hostname: error while loading shared libraries: libc.so.6: cannot change memory protections

โ•ญโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ•ฎ
โ”‚ โ”‚
โ”‚ ๐Ÿ˜ฟ 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. โ”‚
โ”‚ โ”‚
โ•ฐโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ•ฏ

Operating System

None

Driver

None

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions