nvim-devcontainer-cli icon indicating copy to clipboard operation
nvim-devcontainer-cli copied to clipboard

Attempting to use this plugin and use my own dotfiles.

Open alfrye opened this issue 2 months ago • 2 comments

If I want to use my own files and have them cloned from github inside the devcontainer, do I need to use the following config options

nvim_dotfiles_repo = nvim_dotfiles_branch= nvim_dotfiles_directory= nvim_dotfiles_install_command

or do I need to use the

setup_environment configuration options.

also is there a configuration option for specifying a branch when using the setup_environment

Currently we run DevcontainerUp I get an error

Skipping installation: ./packages/zsh.sh. Program already installed. Tue Oct 21 21:15:46 UTC 2025 - Creation of config folders: WARNING! unstowing . would cause conflicts:

  • existing target is neither a link nor a directory: .zshrc
  • All operations aBorted. [Process exited 1]

alfrye avatar Oct 21 '25 21:10 alfrye

Your error is related to trying to use stow to overwrite an existing file . zshrc. You could add something in the install script to remove the existing file.

Those settings you ask about likely don't need to be changed unless you're doing something special.

erichlf avatar Oct 21 '25 21:10 erichlf

Thanks, I don't know where 'stow' is coming from because I am not using 'stow' in my dotfiles. I think it is coming from the plugin's default configuration. I am using nvim_* settings to use my dotfiles.

`return { "arnaupv/nvim-devcontainer-cli", opts = { -- By default, if no extra config is added, following nvim_dotfiles are -- installed: "https://github.com/LazyVim/starter" -- This is an example for configuring other nvim_dotfiles inside the docker container devcontainer_folder=".devcontainer/", nvim_dotfiles_repo = "https://github.com/alfrye/dotfiles", nvim_dotfiles_branch="feature/devcontainer-cli.nvim", nvim_dotfiles_directory="~/nvim_dotfiles", nvim_dotfiles_install_command = "cd ~/nvim_dotfiles/ && ./install.sh", -- In case you want to change the way the devenvironment is setup, you can also provide your own setup -- setup_environment_repo = "", -- setup_environment_install_command = "", }, keys = { -- stylua: ignore { "cdu", ":DevcontainerUp", desc = "Up the DevContainer", }, { "cdc", ":DevcontainerConnect", desc = "Connect to DevContainer", }, } }

alfrye avatar Oct 22 '25 05:10 alfrye