<commit_before># Kubernetes and Vagrant Single-Node Setup

##Forked from https://github.com/coreos/coreos-kubernetes

####**Prerequisites:** 
> Install latest version >= 1.6.2 of Vagrant from [here](https://www.vagrantup.com/downloads.html)  
> Install Vagrant Triggers from a terminal with `vagrant plugin install vagrant-triggers`  
> Install the latest version of Virtual Box from [here](https://www.virtualbox.org/wiki/Downloads)  

####**Setup:**
From your development directory run the following commands.

```sh
git clone <EMAIL>:30x/Dev_Setup.git
cd Dev_Setup/Single-Node
vagrant up
```
These commands will spin up a single node Kubernetes cluster. 

You should also be see the following directory structure:

```
Dev-Setup
├── LICENSE
├── README.md
├── Vagrantfile
├── ctl-setup.sh
├── kubeconfig
├── scripts
├── shared
└── user-data
```

####**Kubectl:**

```kubectl``` is the primary command you will use to interact with your Kubernetes cluster. You should ensure that this is command is in your path. To do this run the following commands:

```sh
wget https://storage.googleapis.com/kubernetes-release/release/v1.2.0/bin/darwin/amd64/kubectl
chmod 755 kubectl
mv kubectl /usr/local/bin
```  
At this point you should have a fully functioning Kubernetes cluster accesible through the ```kubectl``` command. 

###**Docker:**

The VMs docker port is exposed over tcp by default. To remotely access it simply set your `DOCKER_HOST` environment variable with the following command.

```sh
export DOCKER_HOST=172.17.4.99:2375
```
If you plan to use this VM as your default development environment it is recommended that you add the above command to your `.bash_profile` or `.zshrc`.<commit_msg>Updates readme for docker env<commit_after># Kubernetes and Vagrant Single-Node Setup

##Forked from https://github.com/coreos/coreos-kubernetes

####**Prerequisites:** 
> Install latest version >= 1.6.2 of Vagrant from [here](https://www.vagrantup.com/downloads.html)  
> Install Vagrant Triggers from a terminal with `vagrant plugin install vagrant-triggers`  
> Install the latest version of Virtual Box from [here](https://www.virtualbox.org/wiki/Downloads)  

####**Setup:**
From your development directory run the following commands.

```sh
git clone <EMAIL>@github.com:30x/Dev_Setup.git
cd Dev_Setup/Single-Node
vagrant up
```
These commands will spin up a single node Kubernetes cluster. 

You should also be see the following directory structure:

```
Dev-Setup
├── LICENSE
├── README.md
├── Vagrantfile
├── ctl-setup.sh
├── kubeconfig
├── scripts
├── shared
└── user-data
```

####**Kubectl:**

```kubectl``` is the primary command you will use to interact with your Kubernetes cluster. You should ensure that this is command is in your path. To do this run the following commands:

```sh
wget https://storage.googleapis.com/kubernetes-release/release/v1.2.0/bin/darwin/amd64/kubectl
chmod 755 kubectl
mv kubectl /usr/local/bin
```  
At this point you should have a fully functioning Kubernetes cluster accesible through the ```kubectl``` command.

###**Docker:**

The VMs docker port is exposed over tcp by default. To remotely access it simply set your `DOCKER_HOST` environment variable with the following command.

```sh
source docker-setup.sh
```
If you plan to use this VM as your default development environment it is recommended that you add the above command to your `.bash_profile` or `.zshrc`.
{'fraction_non_alphanumeric': 0.11332357247437774, 'fraction_numerical': 0.011127379209370425, 'mean_word_length': 4.750841750841751, 'pattern_counts': {'":': 0, '<': 5, '<?xml version=': 0, '>': 13, 'https://': 8, 'lorem ipsum': 0, 'www.': 4, 'xml': 0}, 'pii_count': 1, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 4, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '4240657', 'n_tokens_mistral': 1085, 'n_tokens_neox': 1040, 'n_words': 409}