nvim-dev-container
A Neovim plugin that provides VSCode-like remote container development support, enabling development inside Docker containers.
What is nvim-dev-container?
devcontainer is a Neovim plugin that enables development inside Docker containers, similar to VSCode's remote container extension. It allows developers to start, attach to, and manage containers defined by `.devcontainer.json` files directly from Neovim, providing a consistent and isolated environment for coding.
Neovim users who work with Docker or Podman containers and want a VSCode-like remote development experience without leaving their editor.
It brings the convenience of VSCode's devcontainer workflow to Neovim, with extensive customization options, support for multiple container runtimes, and seamless integration into existing Neovim configurations.
Overview
Neovim dev container support - Mirror of https://codeberg.org/esensar/nvim-dev-container
Use Cases
Best For
- Developing in isolated Docker environments without switching editors
- Teams using .devcontainer.json files who want Neovim compatibility
- Neovim users who need reproducible development setups across machines
- Projects requiring consistent tooling and dependencies via containers
- Developers who prefer Neovim but need container-based workflows
- Integrating Neovim into existing Docker/Podman development pipelines
Not Ideal For
- Teams already fully invested in VSCode's remote container workflow with its integrated debugging and GUI tools
- Projects that don't use Docker or Podman and rely on simpler virtual environments or local setups
- Users on Neovim versions below 0.12.0 who need reliable client/server mode for seamless container attachment
- Production environments requiring a stable, fully-featured container management solution with extensive support
Pros & Cons
Pros
Embeds Neovim inside containers using client/server mode, providing a unified editing experience without terminal buffers, as highlighted in the requirements for Neovim 0.12.0+.
Offers extensive customization for terminal handling, mounts, container runtime (Docker/Podman), and autocommands, detailed in the setup options with defaults like cache_images and attach_mounts.
Automatically searches for and parses .devcontainer.json files, with template generation for new configurations, ensuring alignment with VSCode workflows and easy project setup.
Caches container images with Neovim installed to speed up subsequent attachments, reducing initialization times, as enabled by default with the cache_images option.
Cons
Explicitly marked as 'WORK IN PROGRESS' in the README, meaning features may be incomplete, buggy, or subject to breaking changes, making it risky for critical workflows.
Requires Neovim 0.12.0+, nvim-treesitter with JSON parser, and a container runtime like Docker or Podman, adding multiple layers of configuration that can overwhelm new users.
Hosted on Codeberg with mailing lists for support, it lacks the large community and extensive documentation of GitHub-based plugins, potentially slowing issue resolution and adoption.
Open Source Alternative To
nvim-dev-container is an open-source alternative to the following products:
Frequently Asked Questions
Related Projects
distant.nvim🚧 (Alpha stage software) Edit files, run programs, and work with LSP on a remote machine from the comfort of your local environment 🚧
nvim-remote-containersDevelop inside docker containers, just like VSCode
remote-sshfs.nvimExplore, edit, and develop on a remote machine via SSHFS with Neovim
netman.nvimNeovim (Lua powered) Network Resource Manager
Found a gem we're missing?
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.