Docker for Fun

Create and run a Docker container to develop and run scripts in a consistent environment.

Docker Scripts

Building the image

> build.sh

The Dockerfile is configured with everything we need to create a Docker image. If anything is changed within the Dockerfile, then update the tag version in the build.sh script.

Running the container for the first time

> start_latest.sh

This will run the Docker image tagged as latest and will drop you into a bash shell session for the running container. You can exit out of the shell using the usual exit command or Ctrl+D.

Note: the to_share folder will be mapped to /home/ubuntu/host within the container

List Previously Running Containers (will show Container IDs)

> list.sh

To see available Docker images, run

> docker images

Restart a Previously Running Container

> restart.sh <container_id>

See list.sh above for retrieve the appropriate container_id

Setup within Running Container

Once you have your Enron container running, you will need to perform some extra tasks.

Setup AWS

Configure AWS CLI. You will need AWS access keys and default region (us-east-1).

> aws configure

Setup Git

> git config --global user.email "you@example.com"
> git config --global user.name "Your Name"

Add ~/.creds file

This file stores credentials. Please request from OPS team.

Update User in ~/.ssh/config file to your personal user account

Change usernames or just copy and paste your ssh config file. If you copy your config, make sure your key names match with what you have in the to_share directory

Develop and Test Scripts

After all of the above setup is successful, you should be able to develop and run any scripts.

Added bash completion for Git commands.

Added ssh-agent startup at login, and ssh-add-rsaid alias so you don't have to keep entering your ssh password when running Git commands.

Proxy for SSH and SCP

Added ssh-proxy-command() and scp-proxy() functions to issue command on remote instance and copy files to remote instance, respectively. These functions require ssh keys to access bastion and any remote instance. See Preparation section for the appropriate SSH keys.

Example of proxying an ssh command:

> ssh-proxy-command bastion <remote-instance-name> 'ls -l'

Example of proxying an scp command:

> scp-proxy bastion <remote-instance-name> <local-path-and-filename> '<remote-path>'