How to handle tmpfiles.d in non-systemd environments

Mon Feb 17 08:32:58 UTC 2020

Hi,
There is a bug [1] showcasing an issue failing in a docker container as
tmpfiles.d there does nothing.

On 6th of December I already wrote to ubuntu-server as part of my daily bug
duties and subscribed people to the bug. Not much happened since then, a
few small IRC exchanges and the Debian init system GR was resolved, but
other than that I didn't hear anything else on the topic.

This class of issues we should IMHO solve/ignore/handle in a general and
not package specific fashion.

I was wondering if anyone on the core-system or systemd side of things has
already thought/decided on that class of issues and could chime in on the
bug.

To everyone - have you seen similar bugs that we should Dup' together in
regard to this?

[1]: https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1855140

-- 
Christian Ehrhardt
Staff Engineer, Ubuntu Server
Canonical Ltd
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/ubuntu-devel/attachments/20200217/a189e0e3/attachment.html>