Adding in updates for Mac for upcoming events #10838
Conversation
|
cool graphics :) |
|
thanks :-) |
| $ $(boot2docker shellinit) | ||
|
|
||
| You can also set them manually by using the `export` commands `boot2docker` | ||
| returns. |
There was a problem hiding this comment.
please don't. The IP address can change randomly, and we've had many users taking the export lines and pasting them into their bashrc / profile.
|
You know, I understand your concern, but unless we show them the correct output to expect, readers won't be able to verify they are running correct. There are several techniques in this document that should help avoid this issue.
The last technique is our standard method in house. Only then do I tell them they can use export. I never actually illustrate setting that value via export on a command line. I can add a line under the original output saying "your IP address will be different" which is just an added safety measure. Pretty standard ops for similar patterns in docs. |
|
|
||
| Work through this section to try some practical container tasks using `boot2docker` VM. | ||
|
|
||
| ### Access container ports |
There was a problem hiding this comment.
from here, this is probably duplicating stuff we have in several places. The programmer in me wants to consolidate and reduce duplication - the reader in my applauds.
There was a problem hiding this comment.
This is a t 8000 eaching technique for this particular situation. It serves several purposes 1) teaches them two new commands 2) If they went away from the page and came back or were interrupted, they can check their terminal.
There was a problem hiding this comment.
yup, more violent agreement :)
Signed-off-by: Mary Anthony <mary.anthony@docker.com>
| green Boot2Docker-x.x.x.pkg button near the bottom of the page.) | ||
| On a typical Linux installation, the Docker client, the Docker daemon, and any | ||
| containers run directly on your localhost. This means you can address ports on a | ||
| Docker container using the standard localhost addressing such as `localhost:8000` or |
| ### Mount a volume on the container | ||
|
|
||
| When you start `boot2docker`, it automatically shares your `/Users` directory | ||
| with the VM. You can use this share to mount directories onto your container. |
|
LGTM with a few copy edits, etc. Good revision. Let's work on always finding the simplest, most pithy to communicate and continue being mindful that we are serving a somewhat diverse group of users in terms of experience. |
|
The first 2 paragraphs still conflate the boot2docker management tool and the Boot2Docker vm: I tried (and thus added words :( ) to simplify it a little like: |
| Once you have an initialized virtual machine, you can control it with `boot2docker stop` | ||
| and `boot2docker start`. | ||
| In OS X, the Docker host address is the address of the Linux VM. | ||
| When you start the `boot2docker` process, the VM is assigned an IP address. Under |
There was a problem hiding this comment.
ug. more conflation. - when you start the Boot2Docker VM, is is assigned an IP address - you don't need to use the boot2docker management tool to start the VM, and you can start the boot2docker management tool with other parameters that don't involve the VM at all
|
I would like to consider discussion on this edit concluded. It's a significant improvement over what was here before, it's largely accurate and has been well vetted. If we see further issues, we can change things down the road. |
|
LGTM as an interim step. +1 to merge. |
Adding in updates for Mac for upcoming events
Signed-off-by: Mary Anthony mary.anthony@docker.com