Re: [systemd-devel] systemd-nspawn leaves leftovers in /tmp

2016-11-11 Thread Lennart Poettering
On Fri, 04.11.16 15:54, Bill Lipa (d...@masterleep.com) wrote: > This might be due to trying to use systemd-nspawn -x with a raw image > inside the btrfs /var/lib/machines volume. It doesn't work in the > sense that the container isn't ephemeral, but there's no error message > either, and this

Re: [systemd-devel] systemd-nspawn leaves leftovers in /tmp

2016-11-04 Thread Bill Lipa
This might be due to trying to use systemd-nspawn -x with a raw image inside the btrfs /var/lib/machines volume. It doesn't work in the sense that the container isn't ephemeral, but there's no error message either, and this leftover gets created. If I jump through elaborate hoops to create the

Re: [systemd-devel] systemd-nspawn leaves leftovers in /tmp

2016-11-03 Thread Lennart Poettering
On Thu, 03.11.16 11:34, Bill Lipa (d...@masterleep.com) wrote: > Hello, > > I am using systemd-nspawn to run a short lived process in a container. > This is a fairly frequent operation (once every few seconds). Each > time systemd-nspawn runs, it leaves a temporary empty directory like >