Can anyone comment on whether its safe to run ceph inside docker?
Docker in Production: An Update
61–70 of 97 posts
Re: Docker in Production: An Update
#62> I am moderately confident that there is no-one on the planet using Docker seriously AND successfully AND without major hassle. Though the tone of this article is very negative, the conclusion is interesting to me as someone that's considered Docker but hasn't done much with it beyond experimenting locally. I'm assuming if there's any forum that has users that can speak to their use of Docker in production, this wou…
We're technically using it in production for my site, www.bugdedupe.com, but we're still in beta, so we haven't experienced heavy usage. We've been using Kubernetes to deploy Docker containers on Google Container Engine, and while there have been a few issues due to Docker/Kubernetes (namely, getting the containers to expose localhost to each other, and to expose themselves to the world), the issues that we've had so…
An interesting comment also from the article:
> Google offers containers as a service, but more importantly, as confirmed by internal sources, their offering is 100% NOT Dockerized.
> Google merely exposes a Docker interface, all the containers are run on internal google containerization technologies, that cannot possibly suffer from all the Docker implementation flaws.
Re: Docker in Production: An Update
#63Every three months or so I tell myself "right,get your finger out, and do something production quality with containers" and come to the same conclusion this guy did.
Have you tried? Make some Dockerfiles, upload to ECR, deploy to an ECS cluster. Hooray, no more dealing with dependency hell and config management.
Re: Docker in Production: An Update
#64Every three months or so I tell myself "right,get your finger out, and do something production quality with containers" and come to the same conclusion this guy did.
Same here. I am trying to use Docker in production since 2014. Production readiness means very different things at different scale. Have you tried LXD? It looks promising.
Re: Docker in Production: An Update
#65While other people just use Docker to serve hundreds of thousands of users (mid size startup) and make money.
Re: Docker in Production: An Update
#66Every three months or so I tell myself "right,get your finger out, and do something production quality with containers" and come to the same conclusion this guy did.
Have you tried? Make some Dockerfiles, upload to ECR, deploy to an ECS cluster. Hooray, no more dealing with dependency hell and config management.
Actually a single JAR and Ansible deployments solve the same problem as well. The number of times I was running into issues with Docker >>> the number of times I was running into issues with single jars and Ansible. Until this stays like that it is not justified to move to Docker. The business use case is to have a reproducible & reliable infrastructure and not to use containers at all cost.
Re: Docker in Production: An Update
#67What about Fedora?
Re: Docker in Production: An Update
#68Re: Docker in Production: An Update
#69Earlier quoted context omitted.
We're technically using it in production for my site, www.bugdedupe.com, but we're still in beta, so we haven't experienced heavy usage. We've been using Kubernetes to deploy Docker containers on Google Container Engine, and while there have been a few issues due to Docker/Kubernetes (namely, getting the containers to expose localhost to each other, and to expose themselves to the world), the issues that we've had so…
An interesting comment also from the article: > Google offers containers as a service, but more importantly, as confirmed by internal sources, their offering is 100% NOT Dockerized. > Google merely exposes a Docker interface, all the containers are run on internal google containerization technologies, that cannot possibly suffer from all the Docker implementation flaws.
As pointed out by https://news.ycombinator.com/item?id=13715358, that's not true.
Re: Docker in Production: An Update
#70Earlier quoted context omitted.
Were you using Device Mapper purposefully, or just because you couldn't get a more typical storage driver to work? The general setup instructions recommend either 1. installing linux-image-extra and using AUFS (for kernel versions = 4). Admittedly, the latter strategy is a bit frustrating and counterintuitive on 16.04. When you install Docker it will start automatically and hang because it can't find the AUFS driver…
So you are saying that all default settings are unusable in production, to the point docker might not start at all, and the only cure is series of 5 obscure advanced system setup/configuration that are almost impossible to figure out by oneself and not documented, yet they should be totally obvious to anyone using Docker, right? FYI: It's because of this sort of bullshit that there are articles called "Docker in Prod…
People like to waste their time on different things. :)