Docker Container(s)

[JoshOrndorff]

We should lower the friction for users/learners to experiment with the recipes. Ultimately, learners should clone the repo and setup a local dev environment, but it isn't realistic to expect everyone to do that, and it certainly isn't realistic for everyone to do that before ever playing around with the recipes.

We could either provide a single docker image that can run any of the recipes nodes, or a docker image for each node. Ideally the image would be built and published through CI. At minimum images should be built for each release to master, and optionally, they could also be built for commits on develop branch.

[TriplEight]

Hey,

1. As it was discussed on the Barcamp, it's worth integrating substrate-developer-hub into our Playground.
2. AFAIU since you are playing around with substrate, you definitely could make use of CI image (this one will become a default soon) which always has the latest compatible Rust and the corresponding toolset.
3. I definitely can add a "how to use this ^ docker image to build locally" to a README (or a recepie)

[JoshOrndorff]

@TriplEight That image seems useful indeed. I'm ready and willing to learn from you and take your advice on this.