To give a sense of scale we have over 1000 containers running at any given time and go through ~15k per day since our containers don't live for very long.
I'm not sure what press is mixed but the industry as a whole has certainly embraced containers. I'd be suspect of any press that determines containers are vaporware and not worth the time.
Disclaimer: I deploy dc/os for customers on prem alongside our paid product.
I am not sold on docker per-se, but it is a reasonably easy choice for a container system available to demand foreign developers on arbitrary platforms standardize on testing with. Containers are auto-generated by the CI/CD system, based on git commits. We're also using gitlab-ce for this.
Multiple iterations on it
1. Orchestration through chef, no service discovery, Just containers on machines as micro-services.
2. Orchestrations through mesos and marathon.
3. Kubernetes and Rundeck.
#3 has been the best in terms of flexibility, #1 has been the best in terms of ease of use and fire-and-forget.
The most complicated part about Docker in production is not actually Docker in production it's everything on the way.
From CI to building to publishing and deployment.
Are you using kubernetes for orchestration?
Is there automation managing the orchestration configurations like Puppet, Chef, Ansible, Saltstack?
Can I assume this is being carried out through virtualization, if so, what kind of hypervisor is in use?
Is this on premise or in the cloud?
More questions to come, I'm sure and thanks in advance for indulging my curiosity!