docker-archive/toolbox

The Docker Toolbox

Docker Toolbox

⚠️ Deprecation Notice: This project and repository is now deprecated and is no longer in active development. Please use Docker Desktop instead where possible. Docker Desktop

Docker released the Docker Toolbox project to make it easier for developers who work on Mac and Windows to get started using Docker. In 2016 Docker released Docker Desktop which superseded toolbox and was significantly easier for the majority of users to get started. This still left some users behind, predominantly users who were on Windows Home editions, Windows 7, Windows 8 and users of VirtualBox. Since 2016 there have been a number of changes. Windows 7 is no longer supported and the mainstream support of Windows 8.1 has ended. The majority of Windows users are now on a version of Windows 10. Since VirtualBox 6.0 users have been able to run VirtualBox and Hyper-V at the same time on their Windows machines, allowing users to use VirtualBox and Docker Desktop side by side on Hyper-V. For Windows Home users, WSL 2 is available and Docker Desktop now uses this to provide Desktop for Windows Home

Given these changes Docker has decided to archive the Toolbox project to allow us to make it clear that we are no longer supporting or developing this product and to give us time to focus on making further improvements to Docker Desktop. Please provide any feedback via the Docker Public Roadmap

==================================

The Docker Toolbox installs everything you need to get started with Docker on Mac OS X and Windows. It includes the Docker client, Compose, Machine, Kitematic, and VirtualBox.

Installation and documentation

Documentation for Mac is available here.

Documentation for Windows is available here.

Note: Some Windows and Mac computers may not have VT-X enabled by default. It is required for VirtualBox. To check if VT-X is enabled on Windows follow this guide here. To enable VT-X on Windows, please see the guide here. To enable VT-X on Intel-based Macs, refer to this Apple guide here. Also note that if the Virtual Machine was created before enabling VT-X it can be necessary to remove and reinstall the VM for Docker Toolbox to work.

Toolbox is currently unavailable for Linux; To get started with Docker on Linux, please follow the Linux Getting Started Guide.

Building the Docker Toolbox

Toolbox installers are built using Docker, so you'll need a Docker host set up. For example, using Docker Machine:

$ docker-machine create -d virtualbox toolbox
$ eval "$(docker-machine env toolbox)"

Then, to build the Toolbox for both platforms:

make

Build for a specific platform:

make osx

or

make windows

The resulting installers will be in the dist directory.

Frequently Asked Questions

Do I have to install VirtualBox?

No, you can deselect VirtualBox during installation. It is bundled in case you want to have a working environment for free.

toolbox's Issues

Kitematic tries to restart my docker-vm

Steps to reproduce:

1. Install Toolbox
2. Start Quickstart Terminal
3. Start Kitematic

Kitematic then says "starting VM" and seems to be stopping and starting the VM that the Quickstart Terminal just created. It seems like Kitematic doesn't recognise the VM that the Terminal created or something like that.

"From your shell" docs need clarification

http://docker-manthony.s3-website-us-east-1.amazonaws.com/installation/mac/#from-your-shell

This is not immediately clear that your not using the Docker CLI.app, particuarly when reading on from the particular section. Probably needs a bit of clarification that these are instructions for something different ("If don't want to use Docker CLI.app and use your own shell, then you can do this...").

Migrate from boot2docker instructions should suggest creating a VM called "dev"

It currently suggests "docker-vm":

$ docker-machine create -d virtualbox --virtualbox-import-boot2docker-vm boot2docker-vm docker-vm

Deleting dev vm through VirtualBox and clicking Docker CLI again causes new dev vm to create in Powered Off state

Start Menu folder name - Docker instead of Docker Inc.

Name it "Docker".

Suggestion: center content

Should we center these two parts of the site?

Environment not Set in Windows DOCKER CLI on startup

I had what I thought was a problem with an old dev. I reinstalled but I am having another problem.

docker-machine ls

$ docker-machine ls
error getting state for host dev: machine does not exist
error getting URL for host dev: machine does not exist
NAME ACTIVE DRIVER STATE URL SWARM
dev * virtualbox Error

Virtual box shows no dev instance....wierd

Suggestion: remove the git messages

Users may be confused - "I thought I just downloaded Docker. Why did git come up?"

The link to the toolbox website should open a new tab

I don't think we want the user to leave the documentation page when he/she clicks on the toolbox website link.

windows 8.1 + IE 11 in VMWare Fusion Pro

Footer copyright icon broken

Need to fix the copyright icon to actually be an icon.

No user flow at the end of installation

On Mac, it's just a close button.

Windows 8.1 installer image not showing correctly

WINDOWS: Start script tries to start vm called dev instead of the other

Mary filing for Jeff

Change Standard install name to Standard

Reason:
Clicked "Customize" to get to the page, not "Custom Install"

Docker CLI.app could suggest to upgrade my dev machine

"Hey - looks like your host called "dev" is running Docker 1.7 but you've just installed Docker Toolbox 1.8. Run "docker-machine upgrade dev" to upgrade it to 1.8."

Feature Request - show product version numbers

ie.) Kitematic v0.8

Missing CONTRIBUTING.md

I noticed there's no "contributing" document in this repository; we might want to add one also mentioning DCO sign-offs etc.

Install text - Kitematic not included

Install text doesn't have Kitematic included.

Suggestion: FAQ - Why no more b2d? Why machine?

Might be a good thing to address this before being asked.

No Docker CLI installed in start menu

Shortcut on desktop but not in start menu folder.

Toolbox could install binaries into separate path

Toolbox could install the binaries to a separate directory somewhere (/Library/...?) and add this to $PATH instead of clobbering stuff in /usr/local/bin. Don't delete my stuff please!

Broken change install location feature

Can't change anything in change install location:

Soln: Can we remove this feature? It doesn't add anything here.

Cannot proceed with install if VirtualBox VMs running

Docs buttons not center aligned

is opt-in to reboot windows still needed with docker-toolbox?

Windows: Docker Quickstart Terminal returns command not found for docker

QuickStart Terminal closes if any error occurs

Images on website are not retina

👀 Including:

• Whale
• Icons
• Logo

"From your shell" section of docs suggest VM called "my-docker-vm"

http://docker-manthony.s3-website-us-east-1.amazonaws.com/installation/mac/#from-your-shell

Should be "dev".

Docker should be called Docker Client in Toolbox

Error creating machine: exit status 1

Cannot create dev vm using docker-machine

You will want to check the provider to make sure the machine and associated resources were properly removed.

Better text when opening up CLI

Currently says:

"The Quick Start CLI is configured to use Docker with the dev VM"

Could say something like:

"The CLI is configured to use Docker with the "dev" machine running at IP address 1.2.3.4.

For help getting started, check out the docs at https://docs.docker.com/..."

VM aborted

Link to Docker Toolbox release page on docs should open a new tab

Under the Installation section, "Go to the Docker Toolbox release page" should open a new tab in the browser so that users don't lose the docs flow.

Windows installation isn't functioning properly

Are we going to fix this before shipping? This happened with the earlier version as well. This is a fresh VM on Fusion. I also saw the same thing on my hardware version.

Automatic or assisted VM upgrades

I already had a machine called dev when I installed the toolbox.
When I launched the CLI I got that error:

Error response from daemon: client and server don't have same version (client : 1.19, server: 1.18)

Because I had Docker 1.6 installed on that machine.
I fixed it with:

machine upgrade dev

But it should be automatized somehow.

Docker Toolbox folder doesn't exist

Text at end of installer says "In the Docker Toolbox folder, open the Docker CLI terminal window." but that folder doesn't exist.

Make .app package

The one thing I don't like here is the installer itself.
Is there a way to uninstall?

Whenever I run an installer on OSX I get a little sick.
Would be nice if the toolbox itself was just a .app package that had UI for install/removal/upgrades.

Machine's import boot2docker VM could default to boot2docker-vm

Needs a change to Machine: docker/machine#1516

Help users quit VirtualBox if toolbox detects it running.

I downloaded DockerToolbox.pkg on OSX, and tried to install it. I was given this screen:

and then dismissing the message exits the installer.

My thoughts as a user are "Well, guess I'm not using Docker Toolbox."

Possible ways to remediate this might be:

• Do the install with virtualbox running anyway. This is ideal. I use lots of virtualbox VMs. Stopping all of them to install some other software on the host is.... not my idea of a fun time.
• At minimum, it should give me the option to continue the installation once I have stopped my virtualbox VMs. Exiting the installer is not a good way to go.

Docker Swarm appears on the index but isn't in the toolbox

We probably don't want to include Swarm on the index page on the mini site because it isn't actually visible in the installer.

Installation picture doesn't fit the whole box

Nightly builds

• Windows: appveyor
• Mac: travisci

Docker Quickstart Terminal returns no such file or directory on .pem file

Mac OS X
rc3

This problem doesn' t happen in a regular terminal

Installed Kitematic icon says alpha

Mac and Windows

Toolbox image needs to be updated

Registry is not a part of the Toolbox installer so please remove the oyster from the toolbox graphic.

Override .bashrc boot2docker scripts

Right now at the end of the Docker CLI start script, $SHELL is run to create a new shell.

We should just default to bash and not open a fresh shell since many users have .bashrc contents that automatically set DOCKER_HOST

Getting started does not allow me to download right away

I had to look around (no search) to find link to download on the next page:

On the next page, it was super hard find the download:

http://docker-manthony.s3-website-us-east-1.amazonaws.com/mac/step_one/

Choppy Docker Quickstart Terminal icon

On Windows replace "You can ssh ..." text as per Mac Changes

The Windows installer still has the "You can ssh into the VM via..." language we replaced on Mac. Sync to the Mac text