Thank you for the development of this plugin. While trying to get it working, I've read through quite a few open and closed issues that have made me wonder if I'm understanding the main use case for this plugin. I hope you can help me understand, as I think nvim-dev-container can help me achieve the workflow I'm going for.
My desired workflow is to run NeoVim (with all of the necessary LSP/Debugging tools I use) within a container. I'd like to attach to the running instance of NeoVim from my local terminal so that I can edit/debug within my container.
In the README, you mention that the "plugin is inspired by jamestthompson3/nvim-remote-containers, but aims to enable having neovim embedded in docker container."
My questions are:
-
Is the above goal of the plugin still to have NeoVim embedded in the devcontainer? I came across issue #30, which makes it sound like you're having to move away from that feature for technical reasons (but maybe I'm misunderstanding the main goal of that specific issue).
-
As mentioned in my first question above, if the main use case is no longer to attach to a container running NeoVim, how does this plugin differ from jamestthompson3/nvim-remote-containers?
-
Does this plugin use the somewhat new client-server functionality in NeoVim?
-
Does this plugin completely follow the specs of VSCode's devcontainer.json. For example, I'm trying to start a container without automatically running the command specified in my Dockerfile by including overrideCommand: true in my .devcontainer.json file but when executing :DevcontainerStart, it executes the Dockerfile CMD.
.devcontainer.json
{
"name": "devcontainer-test",
"build": {
"dockerfile": "Dockerfile"
},
"service": "app",
"dockerComposeFile": "docker-compose.yml",
"overrideCommand": true
}
docker-compose.yml
version:"3.6"services:app:build:.
Dockerfile
FROM python:3.12
WORKDIR /app
COPY . /app
RUN pip install --no-cache-dir -r requirements.txt
CMD ["python", "./main.py"]
Thanks in advance. I'm somewhat new to Docker and even newer to devcontainers so I apologize if I'm missing something obvious in my setup.
Thank you for the development of this plugin. While trying to get it working, I've read through quite a few open and closed issues that have made me wonder if I'm understanding the main use case for this plugin. I hope you can help me understand, as I think `nvim-dev-container` can help me achieve the workflow I'm going for.
My desired workflow is to run NeoVim (with all of the necessary LSP/Debugging tools I use) within a container. I'd like to attach to the running instance of NeoVim from my local terminal so that I can edit/debug within my container.
In the README, you mention that the "plugin is inspired by [jamestthompson3/nvim-remote-containers](https://github.com/jamestthompson3/nvim-remote-containers), but aims to enable having neovim embedded in docker container."
My questions are:
1. Is the above goal of the plugin still to have NeoVim embedded in the devcontainer? I came across [issue #30](https://codeberg.org/esensar/nvim-dev-container/issues/30), which makes it sound like you're having to move away from that feature for technical reasons (but maybe I'm misunderstanding the main goal of that specific issue).
2. As mentioned in my first question above, if the main use case is no longer to attach to a container running NeoVim, how does this plugin differ from [jamestthompson3/nvim-remote-containers](https://github.com/jamestthompson3/nvim-remote-containers)?
3. Does this plugin use the somewhat new [client-server](https://neovim.io/doc/user/remote.html) functionality in NeoVim?
4. Does this plugin completely follow the specs of VSCode's `devcontainer.json`. For example, I'm trying to start a container without automatically running the command specified in my `Dockerfile` by including `overrideCommand: true` in my `.devcontainer.json` file but when executing `:DevcontainerStart`, it executes the `Dockerfile` CMD.
.devcontainer.json
```json
{
"name": "devcontainer-test",
"build": {
"dockerfile": "Dockerfile"
},
"service": "app",
"dockerComposeFile": "docker-compose.yml",
"overrideCommand": true
}
```
docker-compose.yml
```yml
version: "3.6"
services:
app:
build: .
```
Dockerfile
```
FROM python:3.12
WORKDIR /app
COPY . /app
RUN pip install --no-cache-dir -r requirements.txt
CMD ["python", "./main.py"]
```
Thanks in advance. I'm somewhat new to Docker and even newer to devcontainers so I apologize if I'm missing something obvious in my setup.