How We Use Docker For Continuous Delivery – Part 2
contino.co.uk
How We Use Docker For Continuous Delivery – Part 2
1–10 of 29 posts
Re: How We Use Docker For Continuous Delivery – Part 2
#2Re: How We Use Docker For Continuous Delivery – Part 2
#3Re: How We Use Docker For Continuous Delivery – Part 2
#4I wonder how they log from applications in Docker, we found it to be one of the blockers that kept us from using Docker.
Re: How We Use Docker For Continuous Delivery – Part 2
#5I wonder how they log from applications in Docker, we found it to be one of the blockers that kept us from using Docker.
I meant to add that, but essentially we map /var/log in the container to /var/log on the host, and then use rsyslogd to push that into a centralised logstash.
Re: How We Use Docker For Continuous Delivery – Part 2
#6Re: How We Use Docker For Continuous Delivery – Part 2
#7Re: How We Use Docker For Continuous Delivery – Part 2
#8What's the best practice for accessing persistent data from a database system that's in a Docker container?
Re: How We Use Docker For Continuous Delivery – Part 2
#9Minor grip: gray background, gray font. Almost impossible to read unless you're squinting.
Re: How We Use Docker For Continuous Delivery – Part 2
#10I wonder how they log from applications in Docker, we found it to be one of the blockers that kept us from using Docker.
Running a log shipping agent on every docker instance isn't 'free' but it lets you clearly label and manage your logs nicely.