From a6fc3fa7fab71cd0d1a2bfac1deade510cc7e331 Mon Sep 17 00:00:00 2001 From: Wang Jie Date: Sat, 3 Jun 2017 00:59:46 +0800 Subject: [PATCH] Update osx-setup-guide.md (#3442) --- docs/recipes/osx-setup-guide.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/recipes/osx-setup-guide.md b/docs/recipes/osx-setup-guide.md index 73f9ad19e..254e7a9d2 100644 --- a/docs/recipes/osx-setup-guide.md +++ b/docs/recipes/osx-setup-guide.md @@ -12,7 +12,7 @@ This is useful if you intend to run a registry server natively on macOS. You can start a VM on macOS, and deploy your registry normally as a container using Docker inside that VM. -The simplest road to get there is traditionally to use the [docker Toolbox](https://www.docker.com/toolbox), or [docker-machine](/machine/index.md), which usually relies on the [boot2docker](http://boot2docker.io/) iso inside a VirtualBox VM. +The simplest road to get there is traditionally to use the [docker Toolbox](https://www.docker.com/toolbox), or [docker-machine](/machine/index.md), which usually relies on the [boot2docker](http://boot2docker.io/) ISO inside a VirtualBox VM. ### Solution @@ -72,4 +72,4 @@ Start the Docker registry: ### Unloading the docker registry service - launchctl unload ~/Library/LaunchAgents/com.docker.registry.plist \ No newline at end of file + launchctl unload ~/Library/LaunchAgents/com.docker.registry.plist