[NortySpock]

I noticed from the docker overlay filesystem that the container was spraying files all over the disk. (Ephemeral, destroyed on container shutdown, sure, but I wanted to reduce write-wear on my ssd...)

I tried setting it up with /tmp as a tmpfs (ramdisk) but it then refused to start...

Anyone know any broad-spectrum docker incantations to force all overlay writes to RAM, for a container?

[michaelt]

> I wanted to reduce write-wear on my ssd

Modern SSDs are pretty good at things like wear levelling.

For example [1] reports that a bunch of 256 GB SSDs lasted to 2000+ terabytes written, and a handful up to 7000 terabytes written. So you could saturate a 100 megabit internet connection for 5 years before even a small SSD would wear out. And an SSD 4x the size has 4x the life.

If you're running on a raspberry pi with a microsd card for storage, feel free to keep worrying though :)

[1] https://www.reddit.com/r/chia/comments/mukiwz/are_we_overthi...

[lopkeny12ko]

> the container was spraying files all over the disk

Right, that's basically the point...the Warrior downloads files, compresses them, and uploads them for archival. This necessarily requires staging the files somewhere between download and upload.

> Anyone know any broad-spectrum docker incantations to force all overlay writes to RAM, for a container?

Why would you want this? This sounds like a terrible footgun.

[myself248]

The Warrior doesn't resume old jobs after a power cycle, so what's the point of committing anything at all to non-volatile storage?

[rustyminnow]

They say exactly why they want it... "I wanted to reduce write-wear on my ssd"

[j4ah4n]

I think you'll just need to mount it at the right place, with right permissions.

Demonstrated here https://stackoverflow.com/questions/39193419/docker-in-memor...

[Havoc]

You can put the entire docker directory in a ramdisk. Same as you would when trying to move it to a secondary harddisk. Risky though as a reboot would wipe everything