vim-kubernetes VS nvim-docker

Theres quite a few options, most notably I prefer to use https://github.com/dgrbrady/nvim-docker for interacting with containers, along with https://github.com/miversen33/netman.nvim/tree/issue-28-libuv-shenanigans for remote development

I don't remember where I got this code from, but in the plug-in i'm working on, I have the ,w binding set to reload the package. That way, when I make a change I just use that keybinding to reload my changes instead of closing and reopening neovim. Here's the file that sets that up: https://github.com/dgrbrady/nvim-docker/blob/main/dev/init.lua Replace the package name on line 4 and the function call on line 24 with your specific code, then execute :luafile dev/init.lua to load that file to enable the keybinding. you only have to do this once

For example container-layout returns a ContainerLayout whereas container-logs returns _M, and docker return docker

So I spent the past few days writing my first ever Neovim Lua plugin, nvim-docker. It's really early in development and only supports viewing containers on your machine with live reloading of your containers statuses. I have tons of features I'd love to implement, but wanted to get some feedback from the community on the project.