[fChk]

When I mentioned Docker on Mashiro post, I have been replied that using Docker was a no-learning process because it was a nice excercise to set up from scratch the entire STACK applications. So.. I edited this tutorial for that in my mind: allowing the user to perform that guide inside a container.

I disagree!.. There are plenty of basic (and not-so-basic) knowledge worthy to spread while writing(/teaching) about Docker Container technology!.. It just needs you to have enough background on the subject with hands-on experience, while avoiding too much jargon that distract readers, automating tools that obfuscate the subject and unnecessary topics at this level like composition, scheduling and orchestration etc.. The rest is doable even for newbies.

When I mentioned Docker on Mashiro post, I have been replied that using Docker was a no-learning process because it was a nice excercise to set up from scratch the entire STACK applications. So.. I edited this tutorial for that in my mind: allowing the user to perform that guide inside a container.

I think I'm aware of the circumstances in which this tutorial came into being but in any case the result (ie the OP) did a lot of injustice to the whole notion of Docker containers given the hasty way in which it was written.

You see, to my mind, the OP's only real use-case was as a tip to a developer sitting in front of his/here laptop testing @Mashiro's tutorial inside a container then destroy it when everything checks OK!.. Thus it's a way for developers to:
> avoid messing up their own system (if they are using Debian 10) or
> avoid using a full-fledged KVM VM to do that testing instead.

If that's your intention from this tutorial then you should write it in the introduction of the OP for everybody to read and be aware of to avoid having the wrong idea about how Docker containers are run in production.

A better -more didactical- way is to first introduce Docker; what it is? what's for? and then and only then how it's used?