Adding container image for running examples

[bovem]

Added dockerfile for testing examples in a container environment.

Changes

• Added a dockerfile for the image that could be used for running examples.
• Each example folder has a python virtual environment named hamilton that should be activated first before running the example.

Testing

• Build the container image

docker build --tag hamilton-example .

• Creating a container

docker run -it --rm --name hamilton-example hamilton-example

• Running the hello_world example inside the container

cd hamilton/example/hello_world
source hamilton-env/bin/activate
python my_script.py

Notes

Checklist

• PR has an informative and human-readable title (this will be pulled into the release notes)
• Changes are limited to a single goal (no scope creep)
• Code can be automatically merged (no conflicts)
• Code passed the pre-commit check & code is left cleaner/nicer than when first encountered.
• Passes all existing automated tests
• Any change in functionality is tested
• New functions are documented (with a description, list of inputs, and expected output)
• Placeholder code is flagged / future TODOs are captured in comments
• Project documentation has been updated if adding/changing functionality.
• Reviewers requested with the Reviewers tool ➡️

Testing checklist

Python - local testing

• python 3.6
• python 3.7
• python 3.9 (Docker Environment)

[skrawcz]

Just two minor comments, otherwise I ran things and everything worked as specified! Once you have addressed those, this is good to merge. Thanks!

[skrawcz]

Suggested change

	3. Creating a container
	3. Starting your docker container

[skrawcz]

Suggested change

	python my_script.py
	python my_script.py
	deactivate # this will deactivate the python virtual environment, allow you to activate other ones for the other examples.

[skrawcz]

Suggested change

	source hamilton-env/bin/activate
	source hamilton-env/bin/activate # this will activate the virtual environment

[skrawcz]

Can you add something like:

You should be able to run all the examples that have only a requirements.txt. If there are other requirements.txt files (like under data_quality), you'll just need to manually create an environment and install those requirements yourself.

[skrawcz]

Actually you know what, I'll just merge this as is -- since it's just documentation that I'm wanting updates to, I can go ahead and update that after merging and save you the trouble of doing it.

Thanks for your contribution!

[bovem]

Thanks @skrawcz it was fun to work on this issue. I'll keep looking on open issues to see if I could contribute on something else.