Live data from Hacker News

How We Use Docker For Continuous Delivery – Part 2

contino.co.uk

1–10 of 29 posts

Re: How We Use Docker For Continuous Delivery – Part 2

#4
post #3

I 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

#5
post #3

I 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.

Do you have log rotation?

Re: How We Use Docker For Continuous Delivery – Part 2

#8

What's the best practice for accessing persistent data from a database system that's in a Docker container?

Typically, you want to supply the container with a mount point that is outside the container. This way, if the container is replaced, your data isn't impacted.

Re: How We Use Docker For Continuous Delivery – Part 2

#10
post #3

I wonder how they log from applications in Docker, we found it to be one of the blockers that kept us from using Docker.

I use Papertrail but if you want something free...just run Logstash + Kibana + Elastic Search.

Running a log shipping agent on every docker instance isn't 'free' but it lets you clearly label and manage your logs nicely.

Post reply on HN