5 ms·

> If you’re trying to learn Docker you will first have to master its various terminal commands. This is completely the wrong way to go about learning Docker.

by wicket 6y ago

> If you’re trying to learn Docker you will first have to master its various terminal commands. This is completely the wrong way to go about learning Docker. The biggest problem with Docker is that there are too many people using it who claim they know Docker because they learnt a few commands they read on the internet, but they don't actually understand what a container is. In reality, this leads to all sorts of problems, like the deployment of insecure containers in the wild. Guides like this are recipe for disaster.

sosilkj 6y ago
Any recommendations for better learning resources?
- wicket 6y ago
  When I picked up Docker, I had already been using other container technologies for several years so I personally don't know of any modern or complete learning resources that I can recommend. However I would recommend starting out by understanding what namespaces are, i.e. how container isolation works. You should also be aware of what cgroups are and how they are used, but you won't need profound knowledge of them when starting out. The man pages [1] [2] might be a good place to start. [1] http://man7.org/linux/man-pages/man7/namespaces.7.html http://man7.org/linux/man-pages/man7/namespaces.7.html [2] http://man7.org/linux/man-pages/man7/cgroups.7.html http://man7.org/linux/man-pages/man7/cgroups.7.html
gspr 6y ago
Somewhat related to this: although I like to imagine I'm still young (hah!), dynamic and open, I'm quite set in my ways and conservative with software (Debian is my distro of choice on any computer). There's two particular areas where I've tried to learn newfangled stuff over the past few years: deep learning frameworks (because I find the field interesting) and Docker (because it does seem very practical in some circumstances). I feel exhausted by how hard it can be to find good information on either one! Everything I need is usually out there, but it's buried in pages upon pages of google hits that are short recipes or "tutorials" that involve sequencing a bunch of runes without communicating any understanding of what's going on. Does anyone have a good strategy when approaching such hyped up topics (not in particular the aforementioned ones) where almost all sources seem to focus on "just getting it working" and lowering the barrier to entry? I don't mean to promote gatekeeping here, it's just that I personally can't learn from the "just do this then this" style.
- hansvm 6y ago
  A (potentially inefficient) strategy that I use from time to time is to start with some kind of quick start (a hello world container), dive into a basic project with the new tool (what could go wrong if I wrapped up arcanist with Docker?), use that experience to give some context to a moderately in-depth perusal of the docs, and either research or explicitly test (or both) anything that seems unclear. Write any such things down because they're prone to turning into rabbit holes, and you want to cover all of them. With that as a foundation you'll still only know enough to get yourself into trouble, but you'll have the vocabulary and background to be able to find more tailored resources, to immediately reject a lot of articles and guides, to form your own opinions about lists if best practices, and to continue learning via hands-on experience. The underlying assumption is that there are nuggets of wisdom here and there which mostly add up to the knowledge you're looking for, but that they aren't all in the same place and that they're buried under a deluge of inapplicable, SEO'd garbage. I think that's a decent model for thinking about Docker, but other topics like learning most mainstream spoken languages might have more dedicated resources which will serve you better.
- mixedCase 6y ago
  If you don't want to discover things through small steps you practice yourself, you might just want a book on the topic.
- skrtskrt 6y ago
  I just had the same experience digging into Oauth2 and user authentication. Everything “guide” in google search is trying to sell you something, so it just “gets you up and running” with their proprietary software. (Auth0, Google, etc) The Orielly-esque books on the topic are terrible, with terrible explanations paired with terrible code. I’m dying for like a full 100% deep dive on secure, modern web authentication and authorized, with matching code examples, just because I’m so curious about the subject. The best I’ve done so far is to read some open source Oauth code like fosite- but this still doesn’t cover user authentication, or key signing best practices, or secret management or (all the other things I don’t know about but could contribute to an insecure implementation). I feel like I’m at best getting 10% of the picture.

by wicket 6y ago

sosilkj 6y ago

Any recommendations for better learning resources?

wicket 6y ago
When I picked up Docker, I had already been using other container technologies for several years so I personally don't know of any modern or complete learning resources that I can recommend. However I would recommend starting out by understanding what namespaces are, i.e. how container isolation works. You should also be aware of what cgroups are and how they are used, but you won't need profound knowledge of them when starting out. The man pages [1] [2] might be a good place to start. [1] http://man7.org/linux/man-pages/man7/namespaces.7.html http://man7.org/linux/man-pages/man7/namespaces.7.html [2] http://man7.org/linux/man-pages/man7/cgroups.7.html http://man7.org/linux/man-pages/man7/cgroups.7.html

gspr 6y ago

Somewhat related to this: although I like to imagine I'm still young (hah!), dynamic and open, I'm quite set in my ways and conservative with software (Debian is my distro of choice on any computer). There's two particular areas where I've tried to learn newfangled stuff over the past few years: deep learning frameworks (because I find the field interesting) and Docker (because it does seem very practical in some circumstances). I feel exhausted by how hard it can be to find good information on either one! Everything I need is usually out there, but it's buried in pages upon pages of google hits that are short recipes or "tutorials" that involve sequencing a bunch of runes without communicating any understanding of what's going on. Does anyone have a good strategy when approaching such hyped up topics (not in particular the aforementioned ones) where almost all sources seem to focus on "just getting it working" and lowering the barrier to entry? I don't mean to promote gatekeeping here, it's just that I personally can't learn from the "just do this then this" style.

hansvm 6y ago
A (potentially inefficient) strategy that I use from time to time is to start with some kind of quick start (a hello world container), dive into a basic project with the new tool (what could go wrong if I wrapped up arcanist with Docker?), use that experience to give some context to a moderately in-depth perusal of the docs, and either research or explicitly test (or both) anything that seems unclear. Write any such things down because they're prone to turning into rabbit holes, and you want to cover all of them. With that as a foundation you'll still only know enough to get yourself into trouble, but you'll have the vocabulary and background to be able to find more tailored resources, to immediately reject a lot of articles and guides, to form your own opinions about lists if best practices, and to continue learning via hands-on experience. The underlying assumption is that there are nuggets of wisdom here and there which mostly add up to the knowledge you're looking for, but that they aren't all in the same place and that they're buried under a deluge of inapplicable, SEO'd garbage. I think that's a decent model for thinking about Docker, but other topics like learning most mainstream spoken languages might have more dedicated resources which will serve you better.
mixedCase 6y ago
If you don't want to discover things through small steps you practice yourself, you might just want a book on the topic.
skrtskrt 6y ago
I just had the same experience digging into Oauth2 and user authentication. Everything “guide” in google search is trying to sell you something, so it just “gets you up and running” with their proprietary software. (Auth0, Google, etc) The Orielly-esque books on the topic are terrible, with terrible explanations paired with terrible code. I’m dying for like a full 100% deep dive on secure, modern web authentication and authorized, with matching code examples, just because I’m so curious about the subject. The best I’ve done so far is to read some open source Oauth code like fosite- but this still doesn’t cover user authentication, or key signing best practices, or secret management or (all the other things I don’t know about but could contribute to an insecure implementation). I feel like I’m at best getting 10% of the picture.