News for hackers. Stuff that matters.
Re:Lessons from Building a Node App in Docker by z3t4 on Friday April 22, 2016 @04:34AM (#11547781)
The article should mention why you would like to run something in docker. What many forget is that when putting stuff in a container, you create future work for yourself to manage not only your own stuff, but also all the dependencies in the container. If you're just after isolation, that could be accomplished with Linux name-spaces and apparmor.
Re:Lessons from Building a Node App in Docker by jdleesmiller on Friday April 22, 2016 @05:47AM (#11548052)
(Author here.) That's a good question. In this case, the main benefit I was after was easy setup of consistent development environments. We have in the past (and still do) use vagrant + ansible for the same purpose, but Dockerfiles are a lot simpler, and people have been less afraid of changing them vs. the slightly crazy ansible playbooks.

It think it's worked pretty well so far, though we have had a few difficulties:

- Particularly in the early stages of development, we've been changing dependencies a lot, and that requires a lot of image rebuilds. They are very consistent, but also a bit tedious.

- For those of us on macs, using docker machine for development hasn't been all that great, because inotify doesn't work for automatic code reloading (watchify, nodemon, etc.). However, they're hard at work on that with the new Docker for Mac.

I'm hopeful that technologies like kubernetes will make it easier to deploy these containers, too, but I haven't really got there yet. Maybe another article some day!

Re:Lessons from Building a Node App in Docker by xorcist on Friday April 22, 2016 @07:55AM (#11548445)
It's not an either/or scenario. Unless you have a trivial environment, you still need something like Ansible to configure the application in question. Things like setting up monitoring, log transports, certificates, databases etc. needs to be orchestrated outside the container.
Re:Lessons from Building a Node App in Docker by hillbilly on Friday April 22, 2016 @06:21AM (#11548152)
Check out docker-osx-dev which uses rsync to more efficiently synchronize container volumes with your local files and enable watchers.
Re:Lessons from Building a Node App in Docker by saronia on Saturday April 23, 2016 @03:41AM (#11554589)
That seems to work only w/ boot2docker. Is it still applicable in the docker-machine era?
Re:Lessons from Building a Node App in Docker by objectified on Friday April 22, 2016 @08:31AM (#11548614)
I could think of a few reasons why you would like to run something in a Docker container.

- OS packaging is tedious to say the least, and "git clone and pull dependencies on production systems" processes are generally considered messy (if not evil, especially when pulling from repositories hosted on the internet); Docker solves both of these issues by offering a generic interface for shipping and deploying isolated instances of your application. You don't get that with just namespaces and apparmor, you need an API for that (which is really what makes Docker so useful)

- Docker (potentially with the help of its ecosystem) can provide a uniform interface to a couple of the most important operational aspects of an application: logging and monitoring. Especially for heterogeneous or simply large environments, this is a big win.

- When container deployment orchestration matures more, it is much easier to manage and auto-scale your application in a large scale setting since you don't need to reinvent that wheel for every specific stack out there. It will come.

- It makes setting up and understanding development environments easier. Similar to Vagrant, Docker Compose lets you describe your architecture in a config file and easily set up a full stack for you. Especially in companies supporting or developing for a complicated stack, that's very useful. It also probably makes on-boarding of new developers a lot easier.

Still you're making a valid point: you need to maintain those containers. Just like you need to maintain your application's dependencies. Let's be honest though, in many ecosystems that problem already exists: take your typical JEE application that once built, hardly ever upgrades its dependency list anymore (no one even monitors what security holes are being found in all those jars, in many cases). But yes, you should. That problem is really not solved with Docker containers. Most images/containers will be as thin as possible (as will the host OS, preferably), but the concern remains valid.

Re:Lessons from Building a Node App in Docker by collyw on Friday April 22, 2016 @05:36AM (#11548023)
Because its still shiny enough...?
Re:Lessons from Building a Node App in Docker by dominotw on Friday April 22, 2016 @09:59AM (#11549218)
you can scale it up on a generic compute farm like kubernetes?