May Docker Discussion
-
@Bri said in May Docker Discussion:
But that’s what Docker brings to the table that no one else has done (as consumer friendly) yet: containerization on the desktop.
Does it really do that? I can containerize with Snap, Flatpak, LXC, etc. on the desktop just the same, unless I am missing some feature. What does Docker do that I didn't already have?
-
@julian said in May Docker Discussion:
Docker for dev definitely has its applications, I think... the onboarding aspect, as you say.
However, I'm still kind of against docker in production... containers, sure.
This is the biggest problem with Docker, I think, it makes things seem easy for developers and creates invisible challenges for operations.
-
@julian said in May Docker Discussion:
Docker wasn't meant to ease operations, was it? It was mostly to allow devs to sync up their environments to match prod... or so I thought
Neither, I don't think. It isn't fundamentally designed for any production use, the design of it makes little sense for that. The idea was allowing devs to test quickly without going through operational scrutiny. Fast testing, which is where it remains good.
-
-
@julian said in May Docker Discussion:
Case in point https://duo.com/decipher/docker-bug-allows-root-access-to-host-file-system
Ouch...!
Shyte!
-
One thing that I fear from Docker is the community. It's the latest buzzword and hype and because of that, most people using it see it as some magic panacea, and that creates hubris, and hubris leads to instability and insecurity. People who think technology is magic and not subject to the normal rules or rigors are how bad things happen.
-
@scottalanmiller oh you could say that with most of the js libraries that come out. JavaScript has been the new hotness for the last little while and it shows
-
Interesting recent discussion re: Docker
Some parallels to what was discussed here
-
@julian said in May Docker Discussion:
@scottalanmiller oh you could say that with most of the js libraries that come out. JavaScript has been the new hotness for the last little while and it shows
Very true.
-
@julian said in May Docker Discussion:
Interesting recent discussion re: Docker
Some parallels to what was discussed here
Totally true. People put so much into each new thing that they hear about thinking that it is going to change the world, without any clear idea of what problem it is even trying to address!
-
@scottalanmiller said in May Docker Discussion:
Billions wasted on Hadoop startups, the same will eventually be true of Docker | Hacker NewsI'll definitely be using nodeBB in Docker if I end up going with that. I found this thread via the "nodeBB vs Discourse" thread - which I'm still analyzing. It is good that Discourse maintains a Docker image, but wait... Looking into it is a huge monstrosity - and this is going to be a deal breaker if they can't help me use a more striped down setup. I don't want to use their nginx, SSL cert setup, etc... Another check in the box of 'nodeBB'. My main interest is maintainability over a long period of time.
-
@scottalanmiller said in May Docker Discussion:
@Bri said in May Docker Discussion:
But that’s what Docker brings to the table that no one else has done (as consumer friendly) yet: containerization on the desktop.
Does it really do that? I can containerize with Snap, Flatpak, LXC, etc. on the desktop just the same, unless I am missing some feature. What does Docker do that I didn't already have?
Yes, but I'm only coming from the perspective of development experience. Admittedly, I haven't tried any of the things you mentioned, but a cursory search shows that:
- Snap doesn't work on windows yet
- flatpak appears to only work on Linux distros
- Docker is a high level abstraction of LXC, which again only works on Linux kernels
So how much work do you think it would take to get this to work on both Windows (your preferred development machine) and macOS?
You could just give a Linux VM image to devs, or make them dev on a Linux machine, but I've worked that way before (in a VM) and I hated it. Docker has by far been the most portable and reproducible solution for development work that I've experienced.
-
@julian said in May Docker Discussion:
Case in point https://duo.com/decipher/docker-bug-allows-root-access-to-host-file-system
Ouch...!
This article is pure FUD; it's like saying that because a car thief can open your door right after you unlock it and before you get in, all of the locks and the car alarm are useless.
From one of the paragraphs near the end:
This scenario would only be possible if the container was already compromised and a user was using 'docker cp' to replicate the container files and occurred at the same time the copy was being made, a window that is only a few milliseconds.
There were some other, more prominent articles describing root exploits by attaching the docker socket into the container, a scenario which is both unnecessary and uncommon (it would only be used if you're trying to run Docker in Docker).
So while it's not bullet proof (I mean, what technology really is?), it's more secure than installing a random package from the internet with
sudo npm install -
@xenforum said in May Docker Discussion:
I'll definitely be using nodeBB in Docker if I end up going with that.
Like this, it would make dabbling with it more approachable for less technical users (not suggesting that @xenforum is less technical), but
docker-compose upis much easier than, at minimum,- install node (from nodejs.org? nvm? apt-get? brew?)
- clone NodeBB repo
- install Mongo / redis / Postgres (again, multiple ways to do this)
- run
npm install(hopefully not with sudo) - run install script
- (maybe even) install and configure nginx.
The only thing running in docker makes more difficult is developing plugins. I can't house the plugin repo from within
node_modulesbecause for all intents and purposes, the stuff innode_modulesis ephemeral, and you can't symlink from outside the NodeBB root because of the way Docker context works. -
@Bri the helps people who know how to use docker, but it seems it just moves the burden from "installing NodeBB and dependencies" to "installing docker and dependencies, using docker".
Also, there's the question of porting out. It is best practice to run the container with privileged access so it can port out 443 directly or should you run nginx outside the container anyways?
-
I can't believe you guys are having this discussion in 2019. You do realize that virtualization and containerization have become a standard tool nowadays, right? A lot of you sound if you got stuck somewhere in 2010 technology.
