Hi,

just recently, I have written an article about how to deploy an open source application on Linux using Docker. It seems, that Docker is an ideal service for deploying any application on any Linux-machine. I didn't find any drawbacks, but I'm not a developper, I'm just a technical writer What do you think about? Do you use Docker?

This is not a well formed question. Are you having an issue with docker in which you need help? The way you ask your question is like asking "do you like green or blue? Tell me why?" The answer will likely be different depending on who you ask.

Sorry, if my question is not well formed. To write a new article, I'm looking for the information about the issues the developpers or the users have with Docker. I will be so glad, if LQ forum members help me.

Some cautionary statements about Real World Docker use cases.

1 members found this post helpful.

Thank you very much, Habitual! Great article!

it looks like a good article has already been written.

and the wikipedia article is a good read for those who are unfamiliar with Docker

sadly, I am just getting started with Docker.
So, I bought 4 new books on the subject.

I'd be interested in an on-going dialog with someone who knows more than I do about this exciting new technology.
Running CentOS release 6.6 (Final) on a Xen-based virtual host seems wonky, Sometimes I exit a container and I get disco'd from the host system with a Broken pipe message.

Ubuntu 14.04.2 LTS in Virtualbox seems like it's behaving much better. but I haven't made any progress other that pull Debian, Ubuntu, Centos and Fedora images.

So that and print/read/study the http://www.dockerbook.com/TheDockerBook_sample.pdf while I wait for the Docker Book to show up.

Subscribed with interest...

Have a Great Day.

Food for thought:

http://www.vitavonni.de/blog/201503/...ontainers.html

3 members found this post helpful.

It's an interesting question. Docker is so hot right now I think people will use it just to use it.

It solves several problems, none of which would ever exist in a reasonable world.

It does solve an issue with companies wanting to distribute linux software, where only the most popular two distros get the love. That's fantastic.

It solves the issue of open source stacks having become unmanageable nightmares and the resulting dependency hell, but I really feel this problem should truly be solved in the language communities themselves. They've all done an absolutely awful job of it so far. (node, ruby, python, ... and on and on)

They (ruby, node_ python) really need to enforce some standard behaviour on all these libraries (gems, eggs, node modules, etc) developers are pulling into their projects from all over the place. It's pure insanity. I could go on about exactly what, but I think anyone supporting an open source stack in an operational role knows what I'm talking about, if they've not moved to docker already.

EXCELLENT article - thank you!

I have read quite a few articles on Docker, none of which have actually been useful to my understanding and all of which seemed to be more like marketing releases extolling the praises of the latest new and improved!

Twice I have thought to explore by running an instance, but never got past the "Click here and it will download and install everything you need!" point... not on MY systems it won't!

The above linked article is the first I have read on the subject that actually resonated with my own methods and experience and struck all the right nerves!

I am not alone in that feeling!

Amen. The situation has become such a mess in the last five years it blows my mind. I can't believe how ignorant all the devs working in the cloud with ruby and node are about all these issues. They think we should just git pull from github right to the server. Insanity.

I want to be clear, docker does NOT solve this problem, it makes it liveable.

This is the new "devops" mindset. If you want to see a real piece of work, check out Amazon Linux. It's like a middle finger extended to every sysadmin who encounters it.

I would think the "devops" mindset is more along the lines of sysadmins and developers putting their heads together to create the best practices mentioned there. It's not developers pretending to be sysadmins and using bad practices. Though, I hate the term devops. It's a loaded term and over used by people ignorant about it (and even those educated about it). Not that I'm saying you're over-using it. It just gets said way too much around me in life .

In general, following the best practices outlined by phusion baseimage is best no matter what operating system you're using inside of the docker container. Take, for example, this debian based container I created. It takes parts of the phusion baseimage and applies them to Debian. I would do the same on a RHEL/CentOS container or any other operating system. Their python init process is pretty killer.

sag47, you're entirely correct. But in practice, agile is just a buzzword and devops is typically developers pretending to be sysadmins. The word devops actually does have a specification within agile, and it is not a role, it's a methodology - as you described, of sysadmins and developers working together. I just wish I could see it somewhere.

At my company, we're trying to embody it; not doing a terrible job I think. But again, the organization as a whole is still tripping. We might get it right eventually.

how they have been developed seems not much different than how systems have been deployed these days. the technical term i want to use is mashup.

when someone says stack i think of a sand castle on the beach.