[HN Gopher] A definitive guide to Docker in 2023
___________________________________________________________________
A definitive guide to Docker in 2023
Author : taubek
Score : 73 points
Date : 2023-07-08 10:11 UTC (12 hours ago)
(HTM) web link (masteringbackend.com)
(TXT) w3m dump (masteringbackend.com)
| _han wrote:
| Definitive guide to [constantly evolving technology] is never a
| good idea for a title.
| spicyusername wrote:
| That's what the year helps signify, "good right now".
| maronato wrote:
| The title, introduction, and length certainly are misleading.
| It's incomplete even by it's own promises, failing to touch many
| of the topics it lists in the beginning of chapters. It's most
| advanced feature is compose, which is by all means as basic as
| docker features get nowadays. Yet it fails to detail other
| essential features such as networking.
|
| Usually, I would just ignore posts that aren't thorough or are
| inconsistent, but by naming it the "definitive guide" it sets
| itself as a beginner's trap, possibly pushing away, or worse -
| misleading, beginners who could benefit the most from clear
| guides in todays SEO-centric Ad-filled AI-generated world.
|
| Steer clear from this one folks. Docker's official docs are still
| the way to go.
| teilo wrote:
| Ignore the sour grapes. Yes, Docker is constantly evolving. But
| the title _does_ say "in 2023."
|
| I, for one, need tutorials like this, and I am grateful for it.
| Devs who have been using Docker for a while have forgotten how
| intimidating it is for those of us who have our entire dev
| tooling built around VMs (orchestrated with vagrant in my case).
| You need just enough hand holding to get you up and running
| efficiently, and this tutorial does exactly that. It gets you
| over the hump a lot faster than trying to follow years-old and
| incomplete advice from Googling.
|
| Yes, a thing or two may be deprecated. So what? We are used to
| that. But 99% of it still applies.
| DirkH wrote:
| Thank you for the review. You caused me to re-bookmark it after
| reading a warning that it is badly written.
| idoubtit wrote:
| I've only read the first chapter, which is the general
| presentation of Docker, and it's awful. First of all, it's very
| long, with many words and a very low ratio of signal to noise.
|
| Many texts look like they were copied from a Docker commercial.
| For instance the mention of Docker Swarm won't mean anything to
| someone that doesn't already know Swarm. And there's no
| distinction of main components against optional components like
| Swarm.
|
| The final comparison to other container systems is pure junk. It
| should at least mention when the containers are compatible (like
| Podman) or not (like LXC).
|
| I'm sorry for the harsh words. I wondered if I should keep silent
| or prevent other people from wasting their time with this. The
| low quality had me annoyed enough to opt for the latter.
| sp0rk wrote:
| > I'm sorry for the harsh words. I wondered if I should keep
| silent or prevent other people from wasting their time with
| this. The low quality had me annoyed enough to opt for the
| latter.
|
| The harshness of your words don't really have much to do with
| the information you were trying to convey. You could have made
| the same point -- perhaps more convincingly -- if you had
| avoided phrases like "awful" and "pure junk."
| DirkH wrote:
| Thank you for the warning. You caused me to unbookmark it.
| [deleted]
| kqr2 wrote:
| Do you have an alternate recommendation?
| floomk wrote:
| https://docs.docker.com/get-started/
| AugurCognito wrote:
| https://container.training/
|
| Found this to be pretty helpful.
| darnir wrote:
| I thought this was an exaggeration and decided to read it
| nonetheless. Nope, you're right. It's a fluff piece that's
| extremely low signal to noise.
|
| Large parts of it are long winding without getting to the point
| and then it suddenly moves to using terms that haven't been
| introduced.
|
| Avoid this piece.
| selimnairb wrote:
| The first two paragraphs read like they are from a disinterested
| high school book report/generated by ChatGPT.
| politelemon wrote:
| > Nevertheless, Docker runs flawlessly on all major operating
| systems such as Mac, Windows, and Linux with Mac being the
| easiest.
|
| Careful, this gives a false impression. Docker is a Linux tool.
| Windows and Mac docker are indirections, but you're still running
| the commands on Linux. It's Linux that's the simplest easiest and
| most straightforward.
| johanbcn wrote:
| ...and it's already outdated.
|
| Docker compose versioning was deprecated a long time ago.
| kylevedder wrote:
| Related: I recently wrote a blog post about using docker to
| containerize my ML research dev environments -- I've never found
| another way to make properly reproducible dev environments.
| http://vedder.io/misc/research_dev_env.html
___________________________________________________________________
(page generated 2023-07-08 23:01 UTC)