[BUG] `cluster create` terminal output misaligned

[AaronCrawfis]

What did you do

• How was the cluster created?

  • k3d cluster create dev

• What did you do afterwards?

  • Nothing, just watched the output

What did you expect to happen

I expect a cluster to be created, with the progress printed to the terminal

Screenshots or terminal output

Ran it multiple times, the misalignment comes at different times/steps:

PS C:\Repos\myrepo> k3d cluster create dev
INFO[0000] Prep: Network
INFO[0000] Created network 'k3d-dev'
INFO[0000] Created image volume k3d-dev-images
INFO[0000] Starting new tools node...
INFO[0000] Starting Node 'k3d-dev-tools'
INFO[0001] Creating node 'k3d-dev-server-0'
INFO[0001] Creating LoadBalancer 'k3d-dev-serverlb'     
INFO[0001] Using the k3d-tools node to gather environment information 
INFO[0002] Starting cluster 'dev'
INFO[0002] Starting servers...
INFO[0002] Starting Node 'k3d-dev-server-0'
INFO[0008] All agents already running.
INFO[0008] Starting helpers...
INFO[0008] Starting Node 'k3d-dev-serverlb'
INFO[0015] Injecting records for hostAliases (incl. host.k3d.internal) and for 2 network members into CoreDNS configmap...
INFO[0018] Cluster 'dev' created successfully!
                                                        INFO[0018] You can now use it like this:
                                       kubectl cluster-info

PS C:\Repos\myrepo>

INFO[0000] Prep: Network
INFO[0000] Created network 'k3d-dev'
INFO[0000] Created image volume k3d-dev-images
INFO[0000] Starting new tools node...
INFO[0000] Starting Node 'k3d-dev-tools'
INFO[0001] Creating node 'k3d-dev-server-0'
INFO[0001] Creating LoadBalancer 'k3d-dev-serverlb'     
INFO[0001] Using the k3d-tools node to gather environment information 
INFO[0002] Starting cluster 'dev'
INFO[0002] Starting servers...
INFO[0002] Starting Node 'k3d-dev-server-0'
INFO[0007] All agents already running.
INFO[0007] Starting helpers...
INFO[0008] Starting Node 'k3d-dev-serverlb'
INFO[0015] Injecting records for hostAliases (incl. host.k3d.internal) and for 2 network members into CoreDNS configmap...
                                                  INFO[0017] Cluster 'dev' created successfully!
                                 INFO[0017] You can now use it like this:
                kubectl cluster-info

Which OS & Architecture

Windows 10, 21H2
OS Build 19044.1526

Windows Terminal v1.12.10393.0

VS Code v1.64.1

Which version of k3d

k3d version v5.3.0
k3s version v1.22.6-k3s1 (default)

Which version of docker

Client:
 Cloud integration: v1.0.22
 Version:           20.10.11
 API version:       1.41
 Go version:        go1.16.10
 Git commit:        dea9396
 Built:             Thu Nov 18 00:42:51 2021
 OS/Arch:           windows/amd64
 Context:           default
 Experimental:      true

Server: Docker Engine - Community
 Engine:
  Version:          20.10.11
  API version:      1.41 (minimum version 1.12)
  Go version:       go1.16.9
  Git commit:       847da18
  Built:            Thu Nov 18 00:35:39 2021
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.4.12
  GitCommit:        7b11cfaabd73bb80907dd23182b9347b4245eb5d
 runc:
  Version:          1.0.2
  GitCommit:        v1.0.2-0-g52b36a2
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

[iwilltry42]

Hi @AaronCrawfis , thanks for opening this issue!
Can you give this a try in any other terminal emulator?
I've never seen this before and there doesn't seem to be anything on k3d's end that could cause this behavior 🤔
Update: just searched through the code and there's no output other than log output via https://github.com/sirupsen/logrus before that that could somehow magically cause this output 🤔

[AaronCrawfis]

Tried it in Terminal, Command Prompt, and in PowerShell and getting the same results:

Interesting, I'll debug a bit more and see what might be causing the issue. Feel free to close this issue if needed

[iwilltry42]

Ah, but in both cases it's in PowerShell, right?
Anyway, this is super weird.
I just gave this a try in my two Windows 10 VMs with similar setups and didn't see this issue in both cases 🤔

As you suggested, I'm going to close this issue for now, but please feel free to reopen it any time if you think there's anything we can do on k3d's side 👍