In the Kubernetes admin course, we mention CoreOS Tectonic, but it may soon be folded into OpenShift. The slides should be updated to clarify (and, while we're there, add a few other options).

This is in file slides/k8s/setup-selfhosted.md.

[Discussion in #446](https://github.com/jpetazzo/container.training/pull/446/files/3f40cc25a2f31e54a02d64e683deee1be9837e86#diff-2ffe1c2ff95f331d6a12f9ea

Since it is quite common to have long running Minecraft servers and those servers have inherently irreplaceable data the README should include at least one recommendation for backup strategy.

Part of the solution could be extract all of the host directory paths from the mounts section of the container such as with:

docker container inspect -f "{{range .Mounts}}{{.Source}}{{end}}" e718ec

We might need to document how the logs are gathered inside our images and how this can be configured or integrated in a docker landscape.

Related: webdevops/Dockerfile#242

Context

What are you trying to do and how would you want to do it differently? Is it something you currently you cannot do? Is this related to an issue/problem?
Would like to clean the README and create a doc website for using this image.
There is too many sections in the README explaining the different usecases...

Perhaps a doc website using VuePress...

In paragraph 2.3
"2.3. How to use a BioContainer
BioContainers are listed in two main registries:

Docker Hub: Docker-based containers that can use the docker infrastructure.
QUAY Hub: Docker- and rkt-based containers that can use the rkt infrastructure.
For a full documentation about how to use BioContainers to perform bioinformatics analysis, please check the Full Documentation"
There are

We should inspect the client's capabilities.textDocument.signatureHelp.signatureInformation.documentationFormat property to determine what kind of markup the client supports. If it supports Markdown then we should use Markdown in the documentation field of SignatureInformations.

The documentation says that these should be random strings. Usually a public key has a specific relationship to a private key. How are these used? Are they related to bearer tokens on the API? How does one generate tokens to match these? In general, how auth works is poorly explained in the documentation.

It would be great to supplement the articles with real-world examples, e.g. by putting them into this repository and also inviting the scientific community to contribute more via pull requests.

@sje30 suggested "before and after" comparisons of Dockerfiles (nuest/ten-simple-rules-dockerfiles#16 (comment)), which I really like!

**The examples directory

it would be nice to support sharding. relevant information and examples can be found at the following links:

• https://docs.mongodb.com/manual/sharding/
• https://stackoverflow.com/questions/41815916/docker-with-mongodb-3-4-replica-shard
• https://github.com/jfollenfant/mongodb-sharding-docker-compose
• https://github.com/singram/mongo-docker-compose/blob/master/docker-compose.yml

we should