As an alternative solution, I am wondering if we could make this be a cloud-init function to give users control, with a default of /tmp being a tmpfs when memory is sufficient (i.e. if you have less than 1G of RAM, /tmp is tmpfs or you are in a container).
The other area where I think that this change might create a problem is in high density container scenarios (running 200 LXC containers).
As an alternative solution, I am wondering if we could make this be a cloud-init function to give users control, with a default of /tmp being a tmpfs when memory is sufficient (i.e. if you have less than 1G of RAM, /tmp is tmpfs or you are in a container).
The other area where I think that this change might create a problem is in high density container scenarios (running 200 LXC containers).