How do you use Docker?
Hey everybody, let's turn things around for change :)
Today, I would like to ask the community to help us learn more about how folks are using Docker these days. It is a topic that is coming up with increasing frequency, and while we have some thoughts of our own on the topic, and have had discussions with some of you, we would like to hear some more.
Here's a couple of simple questions to get started -
- Do you use Docker, and if so, where: Development? Production?
- How do you deal with logs? Do you get them into Sumo Logic? How?
- What you would like to see from Sumo Logic to streamline logging in a Docker environment?
And that's it already. Please feel free to respond below, or if you prefer, hit me up at christian at sumologic.com.
cheers,
chr.
-
We use Docker a lot in both Development and Production. For now we get logs out to Sumo by sharing a volume and picking them up with a collector on the host. Not ideal, but it works. Hitting up a hosted collector is easy enough as well, just more overhead on the process being containerized, really easy to change the endpoint with a simple env variable at container startup that way. In an ideal world, we'd have collectors embedded in the container, but it would require a new application container every time you changed your collector, which seems like an unnecessary coupling.
Better yet you could provide a docker container with the latest collector and we could just link the containers, or share a volume.
-
We use Docker in production with Elastic Beanstalk. Docker to us, at least at the moment, is simply a means to an end. What we really want is Elastic Beanstalk, but since Playframwork isn't natively supported by EB, wrapping our deployment in a Docker container is the solution, and it works great.
We don't!!!! This is a huge problem for us. EB does allow for the publishing of logs to S3, so it should be possible.
Assuming it's possible already, please create some documentation on how to work with Docker from within EB.
Please sign in to leave a comment.
Comments
2 comments