Rancher - standard_init_linux.go:190: exec user process caused "permission denied"

MrQwenty :

Actually I'm trying to deploy Kubernetes via Rancher on a single server.

I created a new Cluster and added a new node.

But after a several time, an error occurred:

This cluster is currently Provisioning; areas that interact directly with it will not be available until the API is ready.

[controlPlane] Failed to bring up Control Plane: Failed to verify healthcheck: Failed to check https://localhost:6443/healthz for service [kube-apiserver] on host [172.26.116.42]: Get https://localhost:6443/healthz: dial tcp [::1]:6443: connect: connection refused, log: standard_init_linux.go:190: exec user process caused "permission denied"

And when I'm checking my docker container, one of them is always restarting, the rancher/hyperkube:v1.11.3-rancher1

I'm run docker logs my_container_id

And I show standard_init_linux.go:190: exec user process caused "permission denied"

On the cloud vm, the config is:

OS: Ubuntu 18.04.1 LTS Docker Version: 18.06.1-ce Rancher: Rancher v2

Do you have any issues about this error ?

Thank a lot ;)

MrQwenty :

Finally, I called the vm sub-contractor and they created a vm with a nonexec var partition.

After a remount, it's worked.

Collected from the Internet

Please contact [email protected] to delete if infringement.

edited at
0

Comments

0 comments
Login to comment

Related

standard_init_linux.go:190: exec user process caused "exec format error"

standard_init_linux.go:190: exec user process caused "no such file or directory" - Docker

standard_init_linux.go:190: exec user process caused "exec format error" when running Go binary

standard_init_linux.go:190: exec user process caused "no such file or directory" Docker with go basic web app

Docker error: standard_init_linux.go:228: exec user process caused: exec format error

standard_init_linux.go:178: exec user process caused "exec format error"

standard_init_linux.go:211: exec user process caused "exec format error"

Standard_init_linux.go:211: exec user process caused “exec format error”

Docker: standard_init_linux.go:211: exec user process caused "exec format error"

Docker Error: standard_init_linux.go:195: exec user process caused "exec format error"

standard_init_linux.go:207: exec user process caused "exec format error"

standard_init_linux.go:211:exec user process caused "no such file or directory" with alpine linux and python

Docker standard_init_linux.go:228: exec user process caused: no such file or directory

standard_init_linux.go:211: exec user process caused "no such file or directory" on Alpine

Docker: standard_init_linux.go:211: exec user process caused "no such file or directory"

Alpine Image standard_init_linux.go:207: exec user process caused "no such file or directory"

Docker Standard_init_linux.go:207: exec user process caused “no such file or directory”

standard_init_linux.go:219: exec user process caused: no such file or directory

standard_init_linux.go:211: exec user process caused "no such file or directory"?

standard_init_linux.go:219: exec user process caused: no such file or directory - docker problem

standard_init_linux.go:211: exec user process caused "operation not permitted"

starting container process caused "exec: \"/app\": permission denied": unknown

Docker Error standard_init_linux.go:185: exec user process caused "exec format error with Qnap TS131P

Raspberry-pi docker error: standard_init_linux.go:178: exec user process caused "exec format error"

Pip and Powershell inside Docker: standard_init_linux.go:228: exec user process caused: exec format error

Docker run <image> always errs with standard_init_linux.go:207: exec user process caused "no such file or directory" on windows

Docker and php "standard_init_linux.go:207: exec user process caused "exec format error". Also entrypoint fails to read parameters for exec

Starting container process caused "exec: \"/tmp/run.sh\": permission denied": unknown

docker run results in starting container process caused "exec: \"./boot.sh\": permission denied