| |
|---|
| | * How to enable `ssh` access to a `docker` instance |
|---|
| | |
|---|
| | But this is not a "toy" system. What you see here is a public subset |
|---|
| | of what we use all the time here at the TundraWare Intergalactic HQ. |
|---|
| | We use this for software development, testing new distributed computing |
|---|
| | ideas, and doing custom builds in a sanitized environment. |
|---|
| | We use this for software development, testing new distributed |
|---|
| | computing ideas, and doing custom builds in a sanitized environment. |
|---|
| | |
|---|
| | |
|---|
| | # Prep Work: What You Need To Do First |
|---|
| | |
|---|
| |
|---|
| | |
|---|
| | * You've got `docker` already running on your machine |
|---|
| | * You've made `docker` access available to your own login |
|---|
| | * You've got `ansible` installed on your machine |
|---|
| | * `/shared` exists on your host machine with permissions `1777` |
|---|
| | |
|---|
| | |
|---|
| | # Quickstart For The Impatient |
|---|
| | |
|---|
| |
|---|
| | |
|---|
| | # Configuring Sandbox Hostname Resolution |
|---|
| | |
|---|
| | Various parts of this repo assume that there are (up to) 10 running |
|---|
| | sandboxes whose names are `docksand1` through `docksand10`. For this to |
|---|
| | work, you have to configure name resolution to properly associate |
|---|
| | sandboxes whose names are `docksand1` through `docksand10`. For this |
|---|
| | to work, you have to configure name resolution to properly associate |
|---|
| | these names with their equivant IP addresses. |
|---|
| | |
|---|
| | Most likely, you don't have control of your DNS configuration. The |
|---|
| | easy way around this is to add the entries you find in |
|---|
| | `dockerfiles/common/etc/dockersand.hosts` to your own |
|---|
| | `/etc/hosts` file. |
|---|
| | `dockerfiles/common/etc/dockersand.hosts` to your own `/etc/hosts` |
|---|
| | file. |
|---|
| | |
|---|
| | |
|---|
| | # Building The `docker` Image |
|---|
| | |
|---|
| |
|---|
| | |
|---|
| | |
|---|
| | # Logging In |
|---|
| | |
|---|
| | These sandboxes are setup so you can login from your host machine into the running sandboxes |
|---|
| | using `ssh` keys. You will find the keys under `dockerfiles/common/.ssh/`. There is also an `ssh` |
|---|
| | configuration stanza you can add to your own `~/.ssh/config` to get your client to use the |
|---|
| | proper key. |
|---|
| | These sandboxes are setup so you can login from your host machine into |
|---|
| | the running sandboxes using `ssh` keys. You will find the keys under |
|---|
| | `dockerfiles/common/.ssh/`. There is also an `ssh` configuration |
|---|
| | stanza you can add to your own `~/.ssh/config` to get your client to |
|---|
| | use the proper key. |
|---|
| | |
|---|
| | However, it is also possible to login using name (`test`) and password (`test`). |
|---|
| | |
|---|
| | Once you are logged in, you can promote yourself to `root` using the `sudo` command without any |
|---|
| | further password required. |
|---|
| | Once you are logged in, you can promote yourself to `root` using the |
|---|
| | `sudo` command without any further password required. |
|---|
| | |
|---|
| | # Sharing Files |
|---|
| | |
|---|
| | The sandboxes are created to share the `/shared` directory with the |
|---|
| | host machine. Any file you put there is visible from any of the |
|---|
| | sandboxes and/or the host machine. This makes it easy to share or |
|---|
| | move data between the host and any of the sandboxes or between the |
|---|
| | sandboxes themselves. |
|---|
| | |
|---|
| | |
