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

[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 container as a btrfs
subvolume instead of using the pull-raw one liner, the -x flag works
as expected and there is no leftover in /tmp.



On Thu, Nov 3, 2016 at 11:54 AM, Lennart Poettering
<lennart at poettering.net> wrote:
> On Thu, 03.11.16 11:34, Bill Lipa (dojo at masterleep.com) wrote:
>
>>> 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
>> /tmp/nspawn-root-CPeQjR.  These directories don't seem to get cleaned
>> up.
>
> Generally, temporary files like this should not be left around by
> commands that exit cleanly. If they do, then that's a bug, please file
> a bug. (but first, please retry on the two most current systemd
> versions, we only track issues with those upstream).