tiangolo/babun-docker

Use Docker Toolbox with Babun (Cygwin) in Windows

babun-docker

🚨 DEPRECATED 🚨

If you are developing in Windows you will have a much better time using Docker for Windows and developing with WSL (Windows Subsystem for Linux) than using Babun and connecting it to Docker Toolbox. You probably shouldn't use this tool. It's here only for posterity.

Description

Program / fix to allow using Docker Toolbox from Babun or Cygwin in Windows.

If you are using Cygwin, you should be using Babun. It's an improved Cygwin. Nevertheless, the latest versions of babun-docker work in Cygwin too.

This program installs winpty, sets the environment variables and creates a function to embed docker, and to allow non-tty connections.

This allows running commands that "enter" in the container, as for example those that use -it and end in bash:

docker run -it -v $(pwd):/var/www debian bash

It also checks if the default docker-machine (the Virtual Machine) is running, if not, it tries to start it and set the environment to use it.

And it also sets up shared folders in VirtualBox for each drive in your Windows (although you can configure which drives to use if you want) and mounts them inside the virtual machine (docker-machine), to allow using volumes with Docker (from any drive in your Windows, which is even more than what comes by default with the Docker Toolbox) to allow using commands like:

docker run -d -v $(pwd):/var/www ubuntu ping google.com

The shared folders (drives) inside the docker-machine (VirtualBox virtual machine) are mounted in two different directories to make it compatible with docker and docker-compose, so you can use normal relative volumes with docker-compose. You only have to make sure you run a normal docker command first to start and set up everything. For example:

docker ps

Note: After installing babun-docker (this program), you don't have to "use" another program. You can keep using the docker commands as normal. And after running a first docker command, you can use docker-compose as you would normally too.

Installation

• Install Docker Toolbox.
• Run the bundled Docker Quickstart Terminal that comes with Docker Toolbox to make sure everything is working.
• Turn off the Docker Toolbox Virtual Machine: run docker-machine stop default (or turn off the Virtual Machine default in VirtualBox) so that babun-docker can do all the needed automatic configurations with the VM turned off.
• Install Babun and start a terminal.
• Run the following command:

curl -s https://raw.githubusercontent.com/tiangolo/babun-docker/master/setup.sh | source /dev/stdin

• To be able to use babun-docker right away without having to close and open Babun run the update:

babun-docker-update

• From Babun, use Docker as you would normally, for example: docker ps.

It will take care of configuring the virtual machine, turning it on, sharing volumes, allowing non-tty commands, etc. Whenever it does something for you (automatically) you will see an output like: -- babun-docker: doing something.

Note: the installation command will get a script from this repository and run it immediately, performing all the needed steps to install everything (the same steps described in "Manual installation"). If you don't want to run it, you can do a manual installation.

Installing docker-babun in Cygwin

If you definitively don't want to use Babun, you can install docker-babun in Cygwin (nevertheless, I highly recommend you Babun).

First you will need to have installed the following packages (installed by default in Babun):

• curl
• wget
• git

Then you can run the same command as above.

Updating

• To update babun-docker, after following the installation instructions, run the command:

babun-docker-update

Note: if you want to receive email notifications when babun-docker is updated you can "star" this repository (the star button above) and login with GitHub to Sibbell, it will send you notifications automatically with new releases.

Turning off

• As Docker Toolbox runs in a virtual machine, it uses docker-machine to comunicate and configure it. If you want to turn the virtual machine off, run:

docker-machine stop $babun_docker_machine_name

---

Release Notes

Latest changes

• Fix new line CR (Windows style) in setup. PR #37 by @marcelotaube.
• Fix typo in docs. PR #38 by @Jason-Cooke.

2018-04-27:

Updates (winpty) and bug fixes. See PR 34 by murray02.

The return code is now preserved. See PR 31 by ptisserand.

2016-11-09:

Now the shared folders are mounted in two directories inside the VirtualBox virtual machine to make it compatible with docker-compose.

You can start and set up babun-docker and all the shared folders with any docker command, as:

docker ps

And have a docker-compose.yml file with:

version: '2'
services:
  server:
    build: ./server
    volumes:
      - ./server/app:/app
    ports:
      - 8081:80

...note the relative mounted volume in ./server/app:/app.

And then bring up your stack with:

docker-compose up -d

and it will work (because the shared folder paths that docker-compose uses are also mounted in the virtual machine).

2016-08-17:

• Fix for the command docker login, see PR 24 by jpraet.

2016-07-05:

• Make winpty download file explicit, see PR 23 by murrayju.
• Use the latest version of Winpty (0.4.0).

2016-06-22:

• Fix for Docker Beta for Windows, see PR #21 by @ronnypolley.

2016-04-21:

• Now you can run babun-docker in Cygwin (but I still recommend Babun).

2016-04-20:

• Update winpty to latest version (and make old winpty installs to auto-update).
• Now you can use Bash instead of Zsh.

2016-04-19:

• You can configure the VirtualBox installation path with the variable babun_docker_virtualbox_bin. Read more in the Configurations section below.

2016-04-14:

• You can define which specific Windows drives to mount with the variable babun_docker_volumes (by default babun-docker tries to mount them all). Read more in the Configurations section below.

• You can use a separate file in ~/.babun-docker/custom-config.sh for custom configurations. Read more in the Configurations section below.

• Improved mounted volumes and ownership (with hints by @olegweb ).

2016-03-16:

• Support for Docker v1.10 (see PR #9 by @mrkschan ).

2015-11-12:

• babun-docker automatically sets up shared folders in your VirtualBox virtual machine (docker-machine) for each of your Windows drives and mounts them inside the virtual machine, to allow using volumes (from any drive in your Windows, which is even more than what comes by default with the Docker Toolbox) with commands like:

docker run -it -v $(pwd):/var/www debian bash

• You can configure if you want babun-docker to automatically set up VirtualBox shared folders and volumes with the environment variable babun_docker_setup_volumes. Set it to "0" if you want to disable that. Read more in the Configurations section below.

• You can now specify the name of the docker-machine to use with the environment variable babun_docker_machine_name, which is set by default to the "default" machine (named "default"). (No pun / tongue twister intended). Set that environment variable to the name of the machine that you want to use (e.g. babun_docker_machine_name='dev'). Read more in the Configurations section below.

2015-10-21:

• The installation of babun-docker clones the repository and sets up the environment to use the scripts inside it instead of writing it all to the ~/.zshrc file.

• Running babun-docker-update will update that repository (will update babun-docker) and set up the environment again.

---

Docker Volumes with Babun

Here is an explanation of how volumes work in Docker and how they work in the Toolbox Virtual Machine: Docker Volumes with Babun.

That's what allows using commands like:

docker run -it -v $(pwd):/var/www debian bash

But all that is implemented automatically in the newest version of babun-docker.

---

Manual installation

• Go to your home directory:

cd

• clone this repo in the specific directory, like:

git clone https://github.com/tiangolo/babun-docker.git ./.babun-docker

• Enter that directory:

cd ./.babun-docker

• Source the setup:

source ./setup.sh

The setup will:

• Download and install Winpty to allow using Docker commands that enter a container
• Create a command (function) to update babun-docker, with babun-docker-update
• Add itself to the ~/.zshrc file to run at startup
• Run (source) the script to fix Docker, wrapping it

The wrapper script (function) will try to call docker, if it fails, it will check what was the failure, try to fix it and run again.

The wrapper / fix will:

• auto-start the default docker machine
• set the environment variables for that default docker-machine
• use winpty (console) to connect to a tty session to avoid errors, as in:

docker exec -it my_container bash

---

Configurations

After installing babun-docker, you can configure things with environment variables in the file ~/.babun-docker/custom-config.sh.

• If you want to specify which drives should be used for the setup of VirtualBox shared folders and volumes inside your docker-machine virtual machine set the environment variable babun_docker_volumes to a list of the drive names separated by spaces, as in "c d". For example:

echo 'babun_docker_volumes="c d"' >> ~/.babun-docker/custom-config.sh
source ~/.babun-docker/*config.sh

• If you want to disable the setup of VirtualBox shared folders and volumes inside your docker-machine virtual machine set the environment variable babun_docker_setup_volumes to "0". For example:

echo babun_docker_setup_volumes=0 >> ~/.babun-docker/custom-config.sh
source ~/.babun-docker/*config.sh

• If you want to change the virtual machine to use (if you have configured another virtual machine with docker-machine) you can set the environment variable babun_docker_machine_name to the name of your new virtual machine. For example:

echo babun_docker_machine_name='dev' >> ~/.babun-docker/custom-config.sh
source ~/.babun-docker/*config.sh

• If you have VirtualBox installed in a different location (it would be uncommon) you could set the path with the variable babun_docker_virtualbox_bin, you would have to use Cygwin (Babun) paths, you can use cygpath to convert between Windows and Cygwin paths. It should point to the program "VBoxManage". For example:

echo "babun_docker_virtualbox_bin='$(cygpath -u 'C:\Program Files\Oracle\VirtualBox\VBoxManage')'" >> ~/.babun-docker/custom-config.sh
source ~/.babun-docker/*config.sh

---

License

This project is licensed under the terms of the MIT license.

babun-docker's Issues

Problem with volumes

Hi! First of all, thank you for making this. I have been scouring the web for solutions, waiting for this bugfix to appear.. and it did!

It almost all works as expected: I can start babun, then docker, then I get the tty error, then babun-docker springs to life and forwards the parameters to the docker binary.... BUT... I cannot mount any docker volumes with, for example, -v $(pwd)/src:/var/www/. The folders stay empty within the docker container.

Any ideas? I'm assuming it is a problem with winpty not understanding the paths.

Dave

Could not read CA certificate

I have the latest version of babun, babun-docker and Docker Toolbox for Windows installed.

The Docker Quickstart Terminal works as expected, when running a command such as docker run hello-world. When trying to run the same command in Babun, I reveieve the following message: Could not read CA certificate "C:\ca.pem": open C:%

Any thoughts on what the issue might be here?

Docker exec isn't working for machines run outside VirtualBox

Problem is connected with docker machines run on other host like vSphere.

  app git:(develop) ✗ docker-machine ls
NAME      ACTIVE   DRIVER          STATE     URL                        SWARM   DOCKER        ERRORS
default   -        virtualbox      Stopped                                      Unknown
vm        *        vmwarevsphere   Running   tcp://192.168.1.213:2376           v17.04.0-ce

As it could be seen I have vm in started state. Then I wanted to docker exec one of my container.

Error response from daemon: No such container: app_php_1

By docker tutorial I need to do next actions.

➜  app git:(develop) ✗ docker-machine env vm
export DOCKER_TLS_VERIFY="1"
export DOCKER_HOST="tcp://192.168.1.213:2376"
export DOCKER_CERT_PATH="C:\Users\name\.docker\machine\machines\vm"
export DOCKER_MACHINE_NAME="vm"
export COMPOSE_CONVERT_WINDOWS_PATHS="true"
# Run this command to configure your shell:
# eval $("C:\Program Files\Docker Toolbox\docker-machine.exe" env vm)

It suggested to run command above. After that everything would work in standard docker terminal.
I ran this command, but had to modify path I thought

 eval $("/cygdrive/c/Program Files/Docker Toolbox/docker-machine.exe" env vm)

At the end docker exec failed

➜  app git:(develop) ✗ docker exec -it app_php_1 bash
time="2017-04-14T16:47:52+05:00" level=info msg="Unable to use system certificate pool: crypto/x509: system root pool is not available on Windows"
the input device is not a TTY.  If you are using mintty, try prefixing the command with 'winpty'
-- babun-docker: Using winpty
Could not start '"C:/Program Files/Git/cygdrive/c/Program Files/Docker Toolbox/docker" exec -it app_php_1 bash': Не удается найти указанный файл. (error 0x2)

It was not able to find specified path, which seemed incorrect.

Volumes still not working

I let babun-docker set up the directory for my drives in VirtualBox, but when I attach the directory via docker run -v $(pwd):/some/directory -it image I still see an empty directory in /some/directory in my image. The drive seems to be properly listed in VirtualBox as a shared folder, so I'm not sure what's going wrong. :\

bash: console: command not found

Seems like there is some dependency on something called console?

$ docker run -it ubuntu bash
the input device is not a TTY.  If you are using mintty, try prefixing the command with 'winpty'
-- babun-docker: Using winpty
bash: console: command not found

Update winpty to 0.4.3

Winpty is 3 micro versions behind upstream

Line wrapping does not move to new line

Hi,
So I am having this issue on windows 7. If I docker exec -it or run a container and enter a long command the line-wraps somewhere in the middle of the terminal and instead of moving to the next line overwrites the existing line. Any ideas?

Winpty not work

Cant see anything in console (
Commands are running, but not displayed.

Setup does not work when spaces are in PATH

/home/kun/.babun-docker/setup.sh:export:51: not valid in this context: Files/ConEmu:/cygdrive/c/Program

needed to manually put quotes around statement like:
export PATH="$PATH:$babun_docker_winpty_dir"

docker exec not working with Docker for Windows Desktop

Hi,

I tried installing babun-docker to use docker w/ babun. Whenever I use docker commands, I get:

the input device is not a TTY.  If you are using mintty, try prefixing the command with 'winpty'
-- babun-docker: Using winpty

It also seems that the "console" alias is not set. It would be nice to use babun w/ docker but I'm about ready to give up. I've tried running babun-docker-update and updating babun itself but nothing seems to work.

Update winpty

Update winpty, use one of the latest releases and make babun-docker-update also update it.

https://github.com/rprichard/winpty/releases

docker:10: command not found: docker not found

STEPS FOLLOWED:

Open Babun terminal

 echo $0 

Output: ✅
-zsh

 curl -s https://raw.githubusercontent.com/tiangolo/babun-docker/master/setup.sh | source /dev/stdin 

 babun-docker-update 

Output: ✅
-- babun-docker: Updating babun-docker
Already up-to-date.

 docker ps 

Output: ❌
docker:10: command not found: docker not found

Problems under bash

Cool project!

I use bash (unwilling to change). I followed the setup instructions, did curl and update. I had two issues...

First, the winpty binaries were never found by the shell even though the path you set looks correct. Very strange. I copied the winpty*.exe and winpty.dll to my ~/bin folder and then things worked.

Second, every time I run something that invokes babun-docker, I get this...

$ docker exec -it mycontainer ps
the input device is not a TTY.  If you are using mintty, try prefixing the command with 'winpty'
rm: remove regular file ‘/tmp/babun-docker-env-vars’? y
-- babun-docker: Using winpty
  PID TTY          TIME CMD
   70 ?        00:00:00 ps

It always prompts me to delete that "babun-docker-env-vars". I changed "babun-docker.sh" around line 70 to use rm -f when it deletes this file to avoid the prompt.

Hope this is helpful!

Add persistent mount support

Can you:

1. Add some $babun_docker_persistent_volumes="c d" and insert mount command into /mnt/sda1/var/lib/boot2docker/profile
2. Fix mount command to: sudo mount -t vboxsf -o "defaults,uid=id -u docker,gid=id -g docker,iocharset=utf8,rw"

docker-machine on babun gets different results than docker quickstart/cmd

When I first installed babun-docker, running docker-machine ls/start/stop behaved the same as the docker quickstart terminal. However, I upgraded docker toolbox (and virtualbox through the installer), and now when I try starting or stopping my default machine, if a docker-machine isn't already started, it starts one, but virtualbox shows the default box still offline. If one was started in the quickstart terminal, it goes through some work and then just says 'Machine "default" is already started/stopped.", and a docker-machine ps shows the state as Timeout. Starting a new machine goes through the process, I see all the commands of a machine starting, but no new machine starts up in the virtualbox interface. And if I start it in babun first, I can't start anything in quickstart terminal.

This is really frustrating, as it means I can't figure out what's starting my docker machines or where they live, or what settings are running. For now, I'm going to stop using docker with babun, which is frustrating, because it was great being able to use docker with babun.

strange issue using winpty

hi,

from time to time i have this strange error message coming up :(

any ideas where and why ?

Thanks for this great tweak by the way

Unable to communicate with docker when proxy set

When http_proxy is set:
✓ (0) ~ $ docker ps

• docker ps
• [[ -z x ]]
• [[ -z x ]]
• IFS=
• babun_docker_use_winpty=0
• babun_docker_run_again=0
• '/cygdrive/c/Program Files/Docker Toolbox/docker' ps
• read -r line
• echo 'error during connect: Get https://192.168.99.100:2376/v1.36/containers/json: Gateway Timeout'

The solution is to unset http_proxy before communicate with docker container.

diff --git a/bin/babun-docker.sh b/bin/babun-docker.sh
index 0efee21..01e8f0b 100644
--- a/bin/babun-docker.sh
+++ b/bin/babun-docker.sh
@@ -5,6 +5,9 @@ if [[ -z "$docker_bin" ]] ; then
   docker_bin=$(which docker) ;
 fi
 function docker {
+  # Remove proxy
+  PX=$http_proxy
+  unset http_proxy
   if [[ -z ${babun_docker_old_IFS+x} ]] ; then
     babun_docker_old_IFS=$IFS
   fi
@@ -79,4 +82,6 @@ function docker {
    docker $@
  fi
  IFS=$babun_docker_old_IFS
+  http_proxy=$PX
+  export http_proxy
 }

docker run fail: cannot enable tty mode on non tty input

Hello, I use bubun and run below install command successfully, but after that when I run docker info I get error, see below logs:

{ ~ } » curl -s https://raw.githubusercontent.com/tiangolo/babun-docker/master/setup.sh | source /dev/stdin
--2016-04-24 12:26:07-- https://github.com/rprichard/winpty/releases/download/0.2.2/winpty-0.2.2-cygwin-2.4.1-ia32.tar.gz
Resolving github.com (github.com)... 127.8.0.1
Connecting to github.com (github.com)|127.8.0.1|:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://github-cloud.s3.amazonaws.com/releases/3829192/1def7380-dc09-11e5-9d6b-b25fe84177fa.gz?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAISTNZFOVBIJMK3TQ%2F20160424%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20160424T042635Z&X-Amz-Expires=300&X-Amz-Signature=3a12a9cc34c9e0b8595c1b0cda528eb9bd973a186e2d73cd52926574351e2bd7&X-Amz-SignedHeaders=host&actor_id=0&response-content-disposition=attachment%3B%20filename%3Dwinpty-0.2.2-cygwin-2.4.1-ia32.tar.gz&response-content-type=application%2Foctet-stream [following]
--2016-04-24 12:26:36-- https://github-cloud.s3.amazonaws.com/releases/3829192/1def7380-dc09-11e5-9d6b-b25fe84177fa.gz?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAISTNZFOVBIJMK3TQ%2F20160424%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20160424T042635Z&X-Amz-Expires=300&X-Amz-Signature=3a12a9cc34c9e0b8595c1b0cda528eb9bd973a186e2d73cd52926574351e2bd7&X-Amz-SignedHeaders=host&actor_id=0&response-content-disposition=attachment%3B%20filename%3Dwinpty-0.2.2-cygwin-2.4.1-ia32.tar.gz&response-content-type=application%2Foctet-stream
Resolving github-cloud.s3.amazonaws.com (github-cloud.s3.amazonaws.com)... 127.8.0.2
Connecting to github-cloud.s3.amazonaws.com (github-cloud.s3.amazonaws.com)|127.8.0.2|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 738939 (722K) [application/octet-stream]
Saving to: ‘winpty-0.2.2-cygwin-2.4.1-ia32.tar.gz’

winpty-0.2.2-cygwin-2.4. 100%[====================================>] 721.62K 39.0KB/s in 66s s

2016-04-24 12:27:45 (10.9 KB/s) - ‘winpty-0.2.2-cygwin-2.4.1-ia32.tar.gz’ saved [738939/738939]

Cloning into '/home/sguo/.babun-docker'...
remote: Counting objects: 151, done.
remote: Total 151 (delta 0), reused 0 (delta 0), pack-reused 151
Receiving objects: 100% (151/151), 25.94 KiB | 7.00 KiB/s, done.
Resolving deltas: 100% (50/50), done.
Checking connectivity... done.
{ ~ } » docker info
Get http://127.0.0.1:2375/v1.19/info: EOF. Are you trying to connect to a TLS-enabled daemon without TLS?
{ ~ } » docker run -it ubuntu /bin/bash
cannot enable tty mode on non tty input
-- babun-docker: Using winpty
Post http://127.0.0.1:2375/v1.19/containers/create: EOF. Are you trying to connect to a TLS-enabled
daemon without TLS?
{ ~ } » bubun-docker-update
bash: bubun-docker-update: command not found

Any ideas?

uninstall

how to???

docker login issue

I got this error from docker login; I actually want to uninstall babun-docker since it seems to take over my "normal" docker command, e.g.:

 ~/aws  docker login
Warning: failed to get default registry endpoint from daemon (An error occurred trying to connect: Get http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.23/info: open //./pipe/docker_engine: The system cannot find the file specified.). Using system default: https://index.docker.io/v1/
-- babun-docker: Setting VirtualBox shared folder for drive c
VBoxManage.exe: error: The machine 'default' is already locked for a session (or being unlocked)
VBoxManage.exe: error: Details: code VBOX_E_INVALID_OBJECT_STATE (0x80bb0007), component MachineWrap, interface IMachine, callee IUnknown
VBoxManage.exe: error: Context: "LockMachine(a->session, LockType_Write)" at line 1012 of file VBoxManageMisc.cpp
-- babun-docker: Trying to start docker-machine default
Starting "default"...
Machine "default" is already running.
-- babun-docker: Volumes, creating directory for drive: c
-- babun-docker: Volumes, mounting drive: c

Cannot run setup on windows 10

Could not run neither of automatic nor manual setup on babun and have those errors instead;

Automatic

{ ~ }  » curl -s https://raw.githubusercontent.com/tiangolo/babun-docker/master/setup.sh | source /dev/stdin
bash: $'\r': command not found
bash: $'\r': command not found
bash: $'\r': command not found
bash: $'\r': command not found
bash: $'\r': command not found
bash: bin/babun-docker.sh: line 7: syntax error near unexpected token `$'{\r''
'ash: bin/babun-docker.sh: line 7: `function docker {

Manual

{ .babun-docker } master » source ./setup.sh
bash: $'\r': command not found
bash: $'\r': command not found
bash: $'\r': command not found
bash: $'\r': command not found
bash: $'\r': command not found
bash: $'\r': command not found
bash: $'\r': command not found
bash: $'\r': command not found
bash: ./setup.sh: line 78: syntax error near unexpected token `$'{\r''
'ash: ./setup.sh: line 78: `function babun-docker-update {

Error during install.

If I run
curl -s https://raw.githubusercontent.com/tiangolo/babun-docker/master/setup.sh | source /dev/stdin
In babun version 1.2.0, under Windows 10 Professional

{ ~ } » curl -s https://raw.githubusercontent.com/tiangolo/babun-docker/master/setup.sh | source /dev/stdin
grep: '/home/chris/.babun-docker/setup.sh': No such file or directory
{ ~ } »

Bug with Docker Toolbox 1.11.0

The wrapper function doesn't start docker.

Problem connecting with winpty

When I launch docker run-it -v $(pwd):/c/Users/dev2/Projets\ web default bash it shows me that :

cannot enable tty mode on non tty input
babun-docker: Using winpty
Post http://127.0.0.1:2375/v1.20/containers/create: dial tcp 127.0.0.1:2375: ConnectEx tcp: Aucune connexion n'a pu être établie car l'ordinateur cible l'a expressément refusée..

• Are you trying to connect to a TLS-enabled daemon without TLS?
• Is your docker daemon up and running?

docker ps show me that :

Get http://127.0.0.1:2375/v1.20/containers/json: dial tcp 127.0.0.1:2375: ConnectEx tcp: Aucune connexion n’a pu être établie car l’ordinateur cible l’a expressément refusée..
babun-docker: Trying to start docker-machine default
Started machines may have new IP addresses. You may need to re-run the docker-machine env command.
babun-docker: Setting up docker-machine environment
open C:\Users\dev2.docker\machine\machines\default\server.pem: Le fichier spécifié est introuvable.
babun-docker: Running command again

I'm under Windows 8, Babun launched via ConEmu.

How to uninstall?

Where is the uninstall script for babun-docker? I used docker toolbox but i will install docker for windows so I need to un install babun-docker.