mildronize / vim-on-the-fly

VIM via Docker

Vim On The Fly

VIM anywhere

Objective

• Run VIM on the fly on Windows or linux or mac

Prerequisites

• Docker for windows
• Git Client
• Optional: alternative power shell Cmder
• For best appearance using putty and Solarized theme of Putty

Prepare

Run Docoker via Boot2docker Start shortcut on the desktop

or by power shell

PS C:\> cd 'C:\Program Files\Boot2Docker for Windows'
PS C:\> sh start.sh

Instruction

1. Make sure the Docker is running via Boot2docker status. It has to return running. If not go back to previous section

2. Build

   PS C:\> docker build -t vim-on-the-fly .
   

3. Run the container There are 2 choices

   • Use access directly

     docker run -it vim-on-the-fly zsh
     

   • Run the container in the background ( Recommended on Windows )

     1. Run the container in the background (use docker ps to see the process)

     PS C:\> docker run -d -p 2222:22 vim-on-the-fly
     

     2. Log in to it

        • Method 1: Through Docker VM

          PS C:\> boot2docker ssh
          $ ssh root@localhost -p 2222
          

        • Method 2: Through host To use ssh to 192.168.59.104 which is ip of docker VM and port 2222 The password is vimotf that is defined at config/username.

          PS C:\> ssh root@192.168.59.104 -p 2222
          

          Note: You can get the IP of docker VM by boot2docker ip

4. Run vim, Cheer!

   vim
   

Clean up

PS C:\> docker stop run-vimotf
PS C:\> docker rm run-vimotf
PS C:\> docker rmi vim-on-the-fly

Troubleshooting

Problem 1:

If get the message something like that

Get http://127.0.0.1:2375/v1.19/images/json: dial tcp 127.0.0.1:2375: ConnectEx tcp: No connection could be made because the target machine actively refused it.. Are you trying to connect to a TLS-enabled daemon without TLS?

Fix it at boot2docker/boot2docker#952

Problem 2:

Basic volume mount fails with windows docker client against boot2docker #12751 or Problem with -v shared folders in 1.6 #12590

Solution: ahmetalpbalkan said