# Docker container using my boot drive even though I have my volume somewhere else **URL:** \ **Category:** Support\ **Created:** [March 29, 2025, 7:56pm UTC](https://forum.duplicati.com/t/docker-container-using-my-boot-drive-even-though-i-have-my-volume-somewhere-else/20432 "2025-03-29T19:56:17Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![GuitarBilly](https://forum.duplicati.com/user_avatar/forum.duplicati.com/guitarbilly/32/10972_2.png) [@GuitarBilly](https://forum.duplicati.com/u/GuitarBilly)\ **Post date:** [March 30, 2025, 9:52pm UTC](https://forum.duplicati.com/t/docker-container-using-my-boot-drive-even-though-i-have-my-volume-somewhere-else/20432/3 "2025-03-30T21:52:24Z")
@JBinFla, assuming you are on linux; read up on `tmpfs`. That basically creates a file system in RAM which you can mount and use as scratch space for Duplicati tempdir. For example you can create this in /etc/fstab: ```plaintext # duplicati_tmp /mnt/duplicati_tmp tmpfs defaults,size=32G 0 0 ``` I have not used duplicati for a while so I do not know if there are any other cache items to take care of. This thread touches on that: > [@Which directories are used for caching/prestaging?](https://forum.duplicati.com/t/which-directories-are-used-for-caching-prestaging/9580): > > Hey all, I want to make sure the backups don’t really wear out my SSD’s rather quickly so I’m looking into making sure cached data is written to a directory backed by RAM on my host. I’ve mapped /tmp of the duplicati docker container to a folder in /tmp on my host (which resides in RAM). If I’m not mistaking any cache/processing operations that duplicati (docker version) does are (by default) in /tmp, so this should effectively push everything in RAM on my host right? Now I’m still seeing ab… hth. --- _[View the full topic](https://forum.duplicati.com/t/docker-container-using-my-boot-drive-even-though-i-have-my-volume-somewhere-else/20432)._