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

Failed to create kind cluster #3617

Closed
Monokaix opened this issue May 16, 2024 · 3 comments
Closed

Failed to create kind cluster #3617

Monokaix opened this issue May 16, 2024 · 3 comments
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@Monokaix
Copy link

Monokaix commented May 16, 2024

What happened:
Failed to create kind cluster

What you expected to happen:
Install successfully
How to reproduce it (as minimally and precisely as possible):
kind kind create cluster --name test

Anything else we need to know?:

Environment:

  • kind version: (use kind version): kind v0.21.0 go1.21.9 linux/amd64
  • Runtime info: (use docker info, podman info or nerdctl info):
    Client: Docker Engine - Community
    Version: 26.1.2
    Context: default
    Debug Mode: false
    Plugins:
    buildx: Docker Buildx (Docker Inc.)
    Version: v0.14.0
    Path: /usr/libexec/docker/cli-plugins/docker-buildx
    compose: Docker Compose (Docker Inc.)
    Version: v2.27.0
    Path: /usr/libexec/docker/cli-plugins/docker-compose

Server:
Containers: 2
Running: 1
Paused: 0
Stopped: 1
Images: 1
Server Version: 26.1.2
Storage Driver: overlay2
Backing Filesystem: extfs
Supports d_type: true
Using metacopy: false
Native Overlay Diff: true
userxattr: false
Logging Driver: json-file
Cgroup Driver: cgroupfs
Cgroup Version: 1
Plugins:
Volume: local
Network: bridge host ipvlan macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog
Swarm: inactive
Runtimes: io.containerd.runc.v2 runc
Default Runtime: runc
Init Binary: docker-init
containerd version: e377cd56a71523140ca6ae87e30244719194a521
runc version: v1.1.12-0-g51d5e94
init version: de40ad0
Security Options:
seccomp
Profile: builtin
Kernel Version: 4.18.0-348.7.1.el8_5.x86_64
Operating System: CentOS Linux 8
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 15.46GiB
Name: ecs-4b42-0001
ID: b3d59d78-846c-444a-b840-9b4226d2c85a
Docker Root Dir: /var/lib/docker
Debug Mode: false
Experimental: false
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false

  • OS (e.g. from /etc/os-release):
    4.18.0-348.7.1.el8_5.x86_64 Add all the things: port history from test-infra #1 SMP Wed Dec 22 13:25:12 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
  • Kubernetes version: (use kubectl version):
    v1.29.1
  • Any proxies or other special environment settings?:
@Monokaix Monokaix added the kind/bug Categorizes issue or PR as related to a bug. label May 16, 2024
@Monokaix
Copy link
Author

Here are logs exported by kind log.tar.gz

@aojea
Copy link
Contributor

aojea commented May 16, 2024

Cgroup Version: 1
Operating System: CentOS Linux 8

/close

seems dupe of #3558

@k8s-ci-robot
Copy link
Contributor

@aojea: Closing this issue.

In response to this:

Cgroup Version: 1
Operating System: CentOS Linux 8

/close

seems dupe of #3558

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

No branches or pull requests

3 participants