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
> /tmp/nspawn-root-CPeQjR.  These directories don't seem to get cleaned
> up.
> I'm using systemd 229 on Ubuntu 16.04.  The command line looks like:
> sudo systemd-nspawn -axq --private-network --drop-capability=all -u user
>       --chdir /home/user/work -M ubuntu-16.10 --bind
> /home/outer/work:/home/user/work
> I'm a little worried that there are going to be hundreds of thousands
> of these directories clogging up /tmp after a few weeks.  Is this
> expected?

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).


Lennart Poettering, Red Hat
systemd-devel mailing list

Reply via email to