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

Bill Lipa dojo at masterleep.com
Thu Nov 3 18:34:10 UTC 2016


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

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

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

Thank you!
Bill Lipa

More information about the systemd-devel mailing list