Implement tmpfs file system for /tmp that writes to volatile memory instead of persisting to disk

[fuomag9]

Is your feature request related to a problem? Please describe.
I'd love to be able to use /tmp like I would on linux machines, as a tmpfs file system. At the moment the tmpfs file system on WSL 2 is actually implemented by mapping it to disk instead of writing to RAM. This results in files not being cleaned with restarts (e.g. wsl --shutdown) that accumulate over time. Furthermore, this can result in performance issues with code that relies on temp files since they will be actually written to disk.

Describe the solution you'd like
Implement the tmpfs by writing to volatile memory

Describe alternatives you've considered
At least autoclean /tmp in the meantime at the startup of the distro instead of relying on the user to do it.

[therealkenc]

like I would on linux machines, as a tmpfs file system

Label "feature" loophole, but /tmp is not a tmpfs on Real Linux either (on Debian derived distros, anyway). This is for all intents by-design/linux-behavior. If you want /tmp to be tmpfs, you can mount a tmpfs at /tmp. Test for the tmpfs mount in .bashrc, and if it isn't there, mount it.

At least autoclean /tmp in the meantime

That much is dupe #1278 ➡️ #344 (➡️ #994). Fire up cron or just call your tmp cleaning script directly from .bashrc.

[xploSEoF]

As almost all linux machine hardening guides suggest, the /tmp drive should always be mounted as tmpfs with a few additional settings.

As per the recommendations here, doing this directly in the .bashrc isn't ideal but works:

mount|grep -E "^[^ ]* on /tmp " >/dev/null
if [ "$?" != "0" ];then
        echo "Mounting tmp"
        sudo mount -t tmpfs tmpfs /tmp -o noexec,defaults,nodev,nosuid,noatime,size=256m
fi

I've also added this answer to the only stack overflow question I can find on the matter: https://superuser.com/questions/1170939/simulate-reboot-to-clear-tmp-on-the-windows-linux-subsystem/1656653#1656653

[massimosala]

/etc/fstab ... this seems to be creating a new /tmp mount for each bash terminal

@xploSEoF Liam could you please write how to test it?

[mati865]

Since addition of Systemd this can be easily enabled using instruction from this post https://askubuntu.com/a/1416156/588206:

sudo systemctl enable /usr/share/systemd/tmp.mount

[xploSEoF]

/etc/fstab ... this seems to be creating a new /tmp mount for each bash terminal

@xploSEoF Liam could you please write how to test it?

Wow, late reply, sorry.

It's simple. Open a terminal, then put a file into the /tmp drive, even with something as simple as touch /tmp/test then launch another, create another file, and see that neither has the others file.

There are a number of other ways to confirm, and that could be specific to WSL1 - I'm unfortunately stuck on WSL1 due to using features unavailable on WSL2.

[OneBlue]

Indeed you can use either systemd or fstab to use a tmpfs for /tmp. Closing since this is user-configurable.

[Nahor]

Indeed you can use either systemd or fstab to use a tmpfs for /tmp. Closing since this is user-configurable

Note that currently (WSL 2.2.4.0, and since 2.0.12.0), doing so will break GUI applications, because the new tmpfs mount will hide the /tmp/.X11-unix that WSL creates at startup (microsoft/wslg#1156).