K3d: [BUG] k3s node created from k3d exits with status code 255.

Created on 17 Sep 2020 · 4Comments · Source: rancher/k3d

What did you do?

I created a default cluster.

How was the cluster created?

    ~
    ❯ k3d cluster create
    INFO[0000] Created network 'k3d-k3s-default'
    INFO[0000] Created volume 'k3d-k3s-default-images'
    INFO[0001] Creating node 'k3d-k3s-default-server-0'
    INFO[0006] Creating LoadBalancer 'k3d-k3s-default-serverlb'
    INFO[0017] Cluster 'k3s-default' created successfully!  
    INFO[0017] You can now use it like this:
    kubectl cluster-info

What did you do afterwards?

    ~
    ❯ k3d cluster list  
    NAME          SERVERS   AGENTS   LOADBALANCER
    k3s-default   0/1       0/0      true

    ~
    ❯ docker ps -a
    CONTAINER ID        IMAGE                      COMMAND                  CREATED             STATUS                        PORTS                             NAMES
    75d9093ef6fb        rancher/k3d-proxy:v3.0.1   "/bin/sh -c nginx-pr…"   29 seconds ago      Up 23 seconds                 80/tcp, 0.0.0.0:34307->6443/tcp   k3d-k3s-default-serverlb
    444ef9fb956a        rancher/k3s:v1.18.6-k3s1   "/bin/k3s server --t…"   34 seconds ago      Exited (255) 16 seconds ago                                     k3d-k3s-default-server-0

    ~
    ❯ docker logs k3d-k3s-default-server-0  2>&1  |  tee container-logs.txt

What did you expect to happen?

I expected to have a functional test cluster.

Screenshots or terminal output

container-logs (gist)

Which OS & Architecture?

    Operating System       : Arch Linux
    KDE Plasma Version     : 5.19.5
    KDE Frameworks Version : 5.74.0
    Qt Version             : 5.15.1
    Kernel Version         : 5.8.9-arch2-1
    OS Type                : 64-bit
    Processors             : 8 × Intel® Core™ i7-3770 CPU @ 3.40GHz
    Memory                 : 22,9 GiB of RAM
    Graphics Processor     : Mesa DRI Intel® HD Graphics 4000

Which version of k3d?

    ~
    ❯ k3d --version
    k3d version v3.0.1
    k3s version v1.18.6-k3s1 (default)

Which version of docker?

    ~
    ❯ docker version
    Client:
     Version:           19.03.12-ce
     API version:       1.40
     Go version:        go1.14.5
     Git commit:        48a66213fe
     Built:             Sat Jul 18 01:33:21 2020
     OS/Arch:           linux/amd64
     Experimental:      true

    Server:
     Engine:
      Version:          19.03.12-ce
      API version:      1.40 (minimum version 1.12)
      Go version:       go1.14.5
      Git commit:       48a66213fe
      Built:            Sat Jul 18 01:32:59 2020
      OS/Arch:          linux/amd64
      Experimental:     true
     containerd:
      Version:          v1.4.1.m
      GitCommit:        c623d1b36f09f8ef6536a057bd658b3aa8632828.m
     runc:
      Version:          1.0.0-rc92
      GitCommit:        ff819c7e9184c13b7c2607fe6c30ae19403a7aff
     docker-init:
      Version:          0.18.0
      GitCommit:        fec3683

bug

Source

rafael-brandao

All 4 comments

Hi @rafael-brandao , thanks for opening this issue!
I think your issue could be related to issues that we already saw before, related to your filesystem.
Checkout the FAQ: https://k3d.io/faq/faq/#faq-nice-to-know (on btrfs and zfs) :+1: