<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ramdisk on No Subject - nosubject.io -</title><link>https://nosubject.io/en/tags/ramdisk/</link><description>Recent content in Ramdisk on No Subject - nosubject.io -</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Tue, 23 Mar 2021 00:01:29 +0900</lastBuildDate><atom:link href="https://nosubject.io/en/tags/ramdisk/index.xml" rel="self" type="application/rss+xml"/><item><title>[Raspberry Pi] I Thought /var/log Was Safe on a Ramdisk, but Docker Logs Were Being Written to the SD Card</title><link>https://nosubject.io/en/raspberry-pi-ramdisk-docker-logging-driver/</link><pubDate>Tue, 23 Mar 2021 00:01:29 +0900</pubDate><guid>https://nosubject.io/en/raspberry-pi-ramdisk-docker-logging-driver/</guid><description>&lt;p&gt;To extend the life of the SD card, I &lt;a href="https://nosubject.io/raspberry-pi4-ubuntu-20-10-headless-install/#toc7" title="/raspberry-pi4-ubuntu-20-10-headless-install/#toc7" target="_blank" rel="noreferrer noopener"&gt;configured /var/log to live on a Ramdisk&lt;/a&gt;. But Docker logs are output to &lt;strong&gt;/var/lib/docker/containers&lt;/strong&gt;, so of course that did nothing for Docker logs.&lt;/p&gt;
&lt;h4&gt;Test Environment&lt;/h4&gt;
&lt;p&gt;Raspberry Pi 4 (8GB RAM)&lt;br&gt;Ubuntu 20.10 64-bit&lt;/p&gt;
&lt;pre class="wp-block-preformatted"&gt;$ cat /etc/fstab&lt;br&gt;LABEL=writable / ext4 defaults 0 0&lt;br&gt;LABEL=system-boot /boot/firmware vfat defaults 0 1&lt;br&gt;tmpfs /tmp tmpfs defaults,size=128m 0 0&lt;br&gt;tmpfs /var/tmp tmpfs defaults,size=128m 0 0&lt;br&gt;tmpfs /var/log tmpfs defaults,size=64m 0 0&lt;/pre&gt;
&lt;h3&gt;What I Changed&lt;/h3&gt;
&lt;p&gt;Change Docker's logging driver settings. Check the official site for details.&lt;br&gt;Reference: &lt;a href="https://docs.docker.jp/config/container/logging/configure.html#configure-logging-drivers" target="_blank" rel="noreferrer noopener"&gt;Configure logging drivers&lt;/a&gt;&lt;/p&gt;</description></item><item><title>[Raspberry Pi] apt Started Failing After I Put tmp on a Ramdisk</title><link>https://nosubject.io/en/raspberrypi-ramdisk-apt-error/</link><pubDate>Sun, 03 May 2020 12:03:34 +0900</pubDate><guid>https://nosubject.io/en/raspberrypi-ramdisk-apt-error/</guid><description>&lt;p&gt;I configured a Ramdisk to extend the life of the SD card.&lt;br&gt;After that, when I upgraded the kernel with apt, an error occurred because &lt;code&gt;/var/tmp&lt;/code&gt; did not have enough capacity.&lt;/p&gt;
&lt;p&gt;I did not record the error message, but I think it was &lt;code&gt;No space left on device&lt;/code&gt;.&lt;br&gt;I handled it by setting larger sizes for &lt;code&gt;/var/tmp&lt;/code&gt; and similar directories.&lt;/p&gt;
&lt;pre class="wp-block-preformatted"&gt;$ cat /etc/fstab&lt;br&gt;LABEL=writable / ext4 defaults 0 0&lt;br&gt;LABEL=system-boot /boot/firmware vfat defaults 0 1&lt;br&gt;tmpfs /tmp tmpfs defaults,size=128m 0 0&lt;br&gt;tmpfs /var/tmp tmpfs defaults,size=128m 0 0&lt;br&gt;tmpfs /var/log tmpfs defaults,size=64m 0 0&lt;/pre&gt;
&lt;p&gt;The site I used as a reference for extending the SD card life set &lt;code&gt;/var/tmp&lt;/code&gt; to 16MB, and anyone who copied that as-is will probably run into the same thing.&lt;/p&gt;</description></item></channel></rss>