jesseduffield / lazydocker

The lazier way to manage everything docker

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Segfault when launching Lazydocker without root

rgwood opened this issue · comments

Describe the bug
When launching Lazydocker, it immediately fails with the following text:

panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0x81aa83]

goroutine 36 [running]:*Gui).listenForEvents(0xc0000fc420, 0xc0003c6060, 0xc0003860f0)
	/home/runner/work/lazydocker/lazydocker/pkg/gui/gui.go:320 +0x223
created by*Gui).Run
	/home/runner/work/lazydocker/lazydocker/pkg/gui/gui.go:251 +0x34c

To Reproduce
Steps to reproduce the behavior:

  1. Launch lazydocker by typing lazydocker and hitting Enter
  2. See error

Desktop (please complete the following information):

  • OS: Linux (Fedora 36, x64)
  • Lazydocker Version: 0.17.1
  • The last commit id: 011824a9b77874c89ca8a2825be4a9b4a508e217

Additional context
I can reproduce this with the published v0.17.1 binary and when building from source. If I run Lazydocker as root with sudo, Lazydocker works as expected.

I'm not much of a Go developer but if there's anything else I can try to provide useful diagnostics, just let me know!

I'm now realizing that Docker itself was only working under root because I forgot to run these post-install instructions. Might be good to handle this more gracefully than a segfault in Lazydocker, but probably not a high priority.

ezoic increase your site revenue