Create Dockerfile_prod

[JamieTaylor-TUOS]

Added a Dockerfile which:

• Uses python:3.9 as base image
• Installs the PVOutput lib with pip
• Launches a Jupyter notebook server with the example code

Pull Request

Description

This Docker image is useful as a playground and for working interactively with the PVOuput library via Jupyter.

Fixes #63

How Has This Been Tested?

I have built locally as:

>> docker build -t sheffieldsolar/pvoutput:prod-20211118 -f Dockerfile_prod .

And then tested locally:

>> docker run -it --rm -p 1234:1234 -v .pvoutput.yml:/.pvoutput.yml -e PVOUTPUT_CONFIG=/.pvoutput.yml sheffieldsolar/pvoutput:prod-20211118

This successfully launches a Jupyter notebook which can be accessed from the host machine at http://127.0.0.1:1234.

From there, one can edit and run the code in the examples, or create new notebooks.

Note that the config file is being mounted at runtime to /.pvoutput.yml and the env var PVOUTPUT_CONFIG is being set to point to this location. In production, the config file could be added as a secret, in which case the -v flag can be dropped and the PVOUTPUT_CONFIG env var updated to point to the secret.

Note also, that in order to extract data to the host machine or work with persistent notebook files, it would be necessary for the user to also mount a local host directory where notebooks / data can be saved, using either a bind mount or a volume mount. Alternatively, data could be extracted via the internet (e.g. Google Drive).

I have not updated the README to document this Docker image, as I thought it important to have a hosting solution for the image first, so that users are not required to build locally.

Checklist:

• My code follows OCF's coding style guidelines
• I have performed a self-review of my own code
• I have made corresponding changes to the documentation
• I have added tests that prove my fix is effective or that my feature works
• I have checked my code and corrected any misspellings

[JamieTaylor-TUOS]

@JackKelly or @peterdudfield, please could you review this and if happy, add the production image to a Docker repo (Docker Hub maybe?). Then I'll update the README with usage instructions.

I suggest tagging this build as prod or similar (better yet, generate a release and tag it with the prod-<version> or similar). I will submit another PR for a Dockerised development environment in due course.

[JamieTaylor-TUOS]

@flowirtz May prove useful for issue #37

[flowirtz]

NIT: By any chance: Did u try the -slim variant of the image?

It's only ~45MB instead of ~330MB and I generally prefer those to make things smaller and faster.
Should just work out of the box, but sometimes it doesn't.

Suggested change

	FROM python:3.9
	FROM python:3.9-slim

[peterdudfield]

Its it worth putting this in a folder called 'infrastructure/docker' as there will be another (the dev one) docker file soon

[peterdudfield]

Its it worth putting this in a folder called 'infrastructure/docker' as there will be another (the dev one) docker file soon

Here's some code, but we probably need to add some 'key' to this repo
https://github.com/openclimatefix/nowcasting_api/blob/main/.github/workflows/release-docker.yml

[peterdudfield]

Its it worth putting this in a folder called 'infrastructure/docker' as there will be another (the dev one) docker file soon

@JamieTaylor-TUOS shall i do this, and push to this branch?

[peterdudfield]

Ive added issue #76 for pushing the docker file to dockerhub