Is there a way to skip the confirm dialog on stop container?

[JSteunou]

All in the title. I read the doc with no luck, maybe I'm not seeing some options...

[Mathieu-bot]

I don't think there's a built-in way to disable the confirmation dialog at the moment.
A simple workaround is to create a custom command that runs docker stop directly. Since it bypasses Lazydocker's default stop action, the confirmation popup won't appear.
Add this to your ~/.config/lazydocker/config.yml:

customCommands:
  containers:
    - name: stop (no confirm)
      attach: false
      command: 'docker stop {{ .Container.ID }}'

After that, you can trigger the command with c from the containers panel and the container will stop immediately without asking for confirmation.

[SubZtep]

I’m missing this feature too! I only use lazydocker locally, and I’d actually prefer to disable all confirmation dialogs.

Creating a custom command could be a solution, if it were possible to bind a hotkey to it.

I checked out the project, and disabling the confirmation dialog would actually be a pretty simple feature. You could replace the following lines:

lazydocker/pkg/gui/services_panel.go

Lines 226 to 239 in 7e7aadc

	return gui.createConfirmationPanel(gui.Tr.Confirm, gui.Tr.StopService, func(g *gocui.Gui, v *gocui.View) error {
	return gui.WithWaitingStatus(gui.Tr.StoppingStatus, func() error {
	if !gui.isServiceFromLocalProject(service) {
	if service.Container == nil {
	return gui.createErrorPanel(gui.Tr.CannotManageNonLocalService)
	}
	return service.Container.Stop()
	}
	if err := service.Stop(); err != nil {
	return gui.createErrorPanel(err.Error())
	}
	return nil
	})
	}, nil)

with return service.Container.Stop() to remove the confirmation entirely, or add configuration handling instead.

I’m not very familiar with Go, and I couldn’t get the project running smoothly. I asked an LLM agent about an initial startup error, and it immediately started iterating on the code without asking any questions. It modified more than 200 files with tiny changes (missing this and that), and voilà, it worked. But why?