<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Solr on Rowanto Luo</title><link>https://log.rowanto.com/categories/solr/</link><description>Recent content in Solr on Rowanto Luo</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Fri, 30 Oct 2015 00:05:16 +0000</lastBuildDate><atom:link href="https://log.rowanto.com/categories/solr/index.xml" rel="self" type="application/rss+xml"/><item><title>Docker and (Console) Logs Problem</title><link>https://log.rowanto.com/posts/docker-console-logs-problem/</link><pubDate>Fri, 30 Oct 2015 00:05:16 +0000</pubDate><guid>https://log.rowanto.com/posts/docker-console-logs-problem/</guid><description>
&lt;p&gt;Anyone who used docker before and care about quality will have to deal with the logs problem. As we all know, docker runs in a container, and if we don&amp;rsquo;t handle the logs in a special way, the logs will be lost when the container is restarted.&lt;/p&gt;
&lt;p&gt;In order to deal with this, usually we will map the logs folder of our application to the parent host of the container, so that the logs don&amp;rsquo;t get lost when the container is restarted or changed.&lt;/p&gt;</description></item></channel></rss>