Hello,
I have a question: Why should I use dev-container plugin? The reason why I am asking is that I love nvim, but lately I had to move from linux x86/64 to Mac ARM, which means that I need to use docker for a lot of work. When I found your plugin I was really happy because I thought that I will not have to move VS code, whose dev containers work really well (I know that it is created byt Microsoft, so the situation is not really comparable :) ). 

But after trying to run your plugin I got the impression that I get the similar functionality if I directly run docker image with mounted settings, as I need to install the neovim to the every image imageI need to use. So if I do stuff on multiple images, I need to get nvim inside every image. Moreover I guess that I need to install every plugin every time I start developing. So what is the advantage over creating the images with with neovim already prepared?

Thank you for your answer
Michal Tichák

On Tue Aug 15, 2023 at 4:04 PM CEST, Michal Tichák wrote:
> Hello,
> I have a question: Why should I use dev-container plugin? The reason why I am asking is that I love nvim, but lately I had to move from linux x86/64 to Mac ARM, which means that I need to use docker for a lot of work. When I found your plugin I was really happy because I thought that I will not have to move VS code, whose dev containers work really well (I know that it is created byt Microsoft, so the situation is not really comparable :) ). 

Hello! Thank you for your question.
The plugin is still being developed, so I am hoping it will only get
better with time, but right now, it's main purpose is making it easier
to work with containers, especially with containers defined in
devcontainer format (the one VSCode uses).

>
> But after trying to run your plugin I got the impression that I get the similar functionality if I directly run docker image with mounted settings, as I need to install the neovim to the every image imageI need to use. So if I do stuff on multiple images, I need to get nvim inside every image. Moreover I guess that I need to install every plugin every time I start developing. So what is the advantage over creating the images with with neovim already prepared?

Yes, unfortunately, that is correct. Recently I have been making changes
to that and making that process slightly easier, but unfortutely, I
don't think I will be able to get it to the same level as VSCode has
(especially since in some cases they even have prepared images with
VSCode required binaries pre-installed). I wanted to make it a bit
easier by caching these images with nvim preinstalled, but there is
still the issue of having to install it for every image that you use.

Currently the whole experience of using NeoVim inside the container is
not ideal, but this plugin can help more when the devcontainer is more
needed to run beside your editor, available for you to execute some
commands on it.

Do you have specific use-cases in mind that the plugin could cover, that
could potentially be solved by something other than just running neovim
inside the container? As I have found that creating a good experience
based on running neovim inside the container is pretty hard, I am
looking at other options to make working with containers more pleasant
in general.

>
> Thank you for your answer
> Michal Tichák

Thank you for your time and I hope you will find a good use for this
plugin!
Ensar Sarajčić