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

kind create cluster failing #1730

Closed
felixtran39 opened this issue Jul 14, 2020 · 4 comments
Closed

kind create cluster failing #1730

felixtran39 opened this issue Jul 14, 2020 · 4 comments
Labels
kind/support Categorizes issue or PR as a support question. triage/needs-information Indicates an issue needs more information in order to work on it.

Comments

@felixtran39
Copy link

What happened:
Trying to call kind create cluster and it fails at the Writing configuration step. Here is the error message:
ERROR: failed to create cluster: failed to generate kubeadm config content: failed to get kubernetes version from node: failed to get file: command "docker exec --privileged kind-control-plane cat /kind/version" failed with error: exit status 126

What you expected to happen:
Successfully create a cluster when calling kind create cluster.

How to reproduce it (as minimally and precisely as possible):
All I did was download kind (via gcloud components install kind) and then run kind create cluster.

Anything else we need to know?:
I ran with -v 1 flag and got this:

OCI runtime exec failed: exec failed: container_linux.go:349: starting container process caused "process_linux.go:101: executing setns process caused \"exit status 1\"": unknown

Stack Trace: 
sigs.k8s.io/kind/pkg/errors.WithStack
        /src/pkg/errors/errors.go:51
sigs.k8s.io/kind/pkg/exec.(*LocalCmd).Run
        /src/pkg/exec/local.go:116
sigs.k8s.io/kind/pkg/cluster/internal/providers/docker.(*nodeCmd).Run
        /src/pkg/cluster/internal/providers/docker/node.go:130
sigs.k8s.io/kind/pkg/exec.CombinedOutputLines
        /src/pkg/exec/helpers.go:67
sigs.k8s.io/kind/pkg/cluster/nodeutils.KubeVersion
        /src/pkg/cluster/nodeutils/util.go:58
sigs.k8s.io/kind/pkg/cluster/internal/create/actions/config.getKubeadmConfig
        /src/pkg/cluster/internal/create/actions/config/config.go:172
sigs.k8s.io/kind/pkg/cluster/internal/create/actions/config.(*Action).Execute.func1.1
        /src/pkg/cluster/internal/create/actions/config/config.go:84
sigs.k8s.io/kind/pkg/errors.UntilErrorConcurrent.func1
        /src/pkg/errors/concurrent.go:30
runtime.goexit
        /usr/local/go/src/runtime/asm_amd64.s:1357

When calling docker exec --privileged kind-control-plane cat /kind/version, I get
Error: No such container: kind-control-plane

Environment:

  • kind version: (use kind version): kind v0.7.0 go1.13.6 linux/amd64
  • Kubernetes version: (use kubectl version):
Client Version: version.Info{Major:"1", Minor:"15+", GitVersion:"v1.15.11-dispatcher", GitCommit:"f2a77f678d6baccda27740d700f6cba2754dfacf", GitTreeState:"clean", BuildDate:"2020-04-21T04:42:07Z", GoVersion:"go1.12.17", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"15+", GitVersion:"v1.15.11-gke.15", GitCommit:"8ce551a0c972a9f113e326df0537aa3f1798d93e", GitTreeState:"clean", BuildDate:"2020-05-05T18:38:03Z", GoVersion:"go1.12.17b4", Compiler:"gc", Platform:"linux/amd64"}
  • Docker version: (use docker info): 19.03.12
  • OS (e.g. from /etc/os-release): Debian GNU/Linux 10 (buster)
@felixtran39 felixtran39 added the kind/bug Categorizes issue or PR as related to a bug. label Jul 14, 2020
@BenTheElder
Copy link
Member

BenTheElder commented Jul 14, 2020

OCI runtime exec failed: exec failed: container_linux.go:349: starting container process caused "process_linux.go:101: executing setns process caused "exit status 1"": unknown

this is a failure in docker / runc

can you tell me more about your environment?

an yreason to not use the latest kind release? install method, I see

@BenTheElder
Copy link
Member

This means we can't docker exec into the node container from the host. Probably your docker environment has a bug.

can you share docker info?

@BenTheElder
Copy link
Member

opencontainers/runc#1740
moby/moby#40399

It appears this usually happens due to running out of memory, it can also happen with userns-remap enabled moby/moby#31037, there seem to be a number of reasons.

moby/moby#25929

they're not related to anything kind is doing though

@BenTheElder BenTheElder added kind/support Categorizes issue or PR as a support question. triage/needs-information Indicates an issue needs more information in order to work on it. and removed kind/bug Categorizes issue or PR as related to a bug. labels Jul 14, 2020
@felixtran39
Copy link
Author

Thank you for the replies. I am using Crostini and apparently that has issues with Docker so that seems to be why this error was happening.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/support Categorizes issue or PR as a support question. triage/needs-information Indicates an issue needs more information in order to work on it.
Projects
None yet
Development

No branches or pull requests

2 participants