1
0
mirror of https://github.com/SpaceVim/SpaceVim.git synced 2025-01-23 07:20:04 +08:00
SpaceVim/docker
2022-05-27 12:49:17 +08:00
..
Dockerfile fix(docker): fix docker entrypoint 2022-05-27 12:49:17 +08:00
init.toml chore(copyright): update email 2022-03-27 13:38:54 +08:00
Makefile fix(docker): fix docker configuration 2022-05-23 21:32:03 +08:00
README.md docs(docker): add link to docker hub 2022-05-23 22:12:46 +08:00

SpaceVim in DockerHub

Docker Automated build Docker Image Size (latest by date) Docker Pulls

This Dockerfile builds neovim HEAD and installs the latest available version of SpaceVim. You might want to use this for several reasons:

  • Have a consistent version of Neovim and SpaceVim as long as the machine supports Docker.
  • Try SpaceVim without modifying your current Vim/Neovim configuration.
  • Try the latest Neovim with SpaceVim.
  • Try SpaceVim with a newer version of Python.
  • Debug SpaceVim configurations. e.g. when posting a bug report if you can reproduce it in this container then there's a higher chance that it is a true bug and not just an issue with your machine.

FAQ

Isn't Docker stateless? Won't I have to reinstall all plugins each time I launch the container?

  • During the build we call dein#install() so all plugins are installed and frozen. Your custom configurations can be added as an additional build step using the Docker COPY command.

Build

You can build using the supplied Makefile:

make build

or call the command manually using:

docker build -t nvim -f Dockerfile .

Run

You can run the container using:

docker run -it nvim

but that isn't terribly useful since changes made inside the container won't be visible outside. More useful is mounting the current working directory inside the container:

docker run -it -v $(pwd):/home/spacevim/src nvim

Even better is an alias dnvim which will do this automatically:

alias dnvim='docker run -it -v $(pwd):/home/spacevim/src nvim'