How to handle tmpfiles.d in non-systemd environments
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| haproxy (Ubuntu) |
Opinion
|
Undecided
|
Unassigned | ||
| systemd (Ubuntu) |
New
|
High
|
Unassigned | ||
Bug Description
This is a general issue about systemd features like tmpfiles.d which won't run in some environments like docker containers.
Packages more and more rely on that with haproxy being the example that opened the bug, but clearly not the only one.
I wanted to add tasks for all affected, but a qucik check showed that there are almost to many.
$ apt-file search tmpfiles.d | cut -d':' -f 1 | sort | uniq
129 at the moment and probably increasing.
List of affected as of Dec 2019:
acmetool anytun apt-cacher-ng bacula-common bind9 binkd bley bzflag-server ceph-common certmonger cockpit-ws colord connman courier-authdaemon courier-imap courier-ldap courier-mlm courier-mta courier-pop cryptsetup-bin cyrus-common dbus dhcpcanon diaspora-common dnssec-trigger ejabberd fail2ban firebird3.0-server freeipa-client freeipa-server glusterfs-server gvfs-common haproxy hddemux heartbeat htcondor i2pd inn inspircd iodine knot knot-resolver krb5-otp laptop-mode-tools lemonldap-
Handling of these heavily Depends on the recent Debian GR [1].
I'd suggest we wait how that turns out and then need to consider how (if?) to handle it in a central place, probably systemd or a derivative tool as started to be discussed in [2]
If possible I'd avoid fixes in individual packages as it encourages growth of various workarounds for a problem that needs a general solution.
[1]: https:/
[2]: https:/
--- Original report below ---
When installing the haproxy package from the current Ubuntu 18.04 Bionic repos, the package does not install the directory /run/haproxy. This directory is mentioned in the default config file /etc/haproxy/
stats socket /run/haproxy/
Starting HAProxy manually will show the following error:
# /usr/sbin/haproxy -f /etc/haproxy/
[ALERT] 337/154339 (24) : Starting frontend GLOBAL: cannot bind UNIX socket [/run/haproxy/
After manual creation of the directory, the start works:
# mkdir /run/haproxy
# /usr/sbin/haproxy -f /etc/haproxy/
# ps auxf
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
root 10 0.1 0.0 18616 3416 pts/0 Ss 15:42 0:00 /bin/bash
root 32 0.0 0.0 34400 2900 pts/0 R+ 15:45 0:00 \_ ps auxf
root 1 0.0 0.0 18376 3016 ? Ss 15:40 0:00 bash /root/entrypoint.sh
haproxy 31 0.0 0.0 54284 1252 ? Ss 15:45 0:00 /usr/sbin/haproxy -f /etc/haproxy/
This can be reproduced with a simple Docker container the following Dockerfile:
-------
FROM ubuntu:18.04
MAINTAINER Claudio Kuenzler <email address hidden>
# install packages
RUN apt-get update \
&& apt-get install -y -qq haproxy
CMD ["/usr/
-------
Checking the haproxy package for the run directory shows nothing:
# dpkg -L haproxy | grep run ; date
Wed Dec 4 15:58:52 UTC 2019
*******
Update: After analysis of the haproxy package (see https:/
Suggestion: Do not rely on Systemd to create /run/haproxy. Maybe use debian/
| description: | updated |
| summary: |
- haproxy package misses creation of default socket path + haproxy package misses creation of default stats socket path |
| description: | updated |
| description: | updated |
| Christian Ehrhardt (paelzer) wrote Re: haproxy package misses creation of default stats socket path | #1 |
| tags: | added: server-triage-discuss |
| Claudio Kuenzler (napsty) wrote | #2 |
| summary: |
- haproxy package misses creation of default stats socket path + haproxy package misses creation of default stats socket path in Docker + container |
| Claudio Kuenzler (napsty) wrote Re: haproxy package misses creation of default stats socket path in Docker container | #3 |
| Christian Ehrhardt (paelzer) wrote | #4 |
| Christian Ehrhardt (paelzer) wrote | #5 |
| summary: |
- haproxy package misses creation of default stats socket path in Docker - container + How to handle tmpfiles.d in non-systemd environments |
| description: | updated |
| Changed in haproxy (Ubuntu): | |
| status: | New → Opinion |
| Changed in systemd (Ubuntu): | |
| importance: | Undecided → High |
| Christian Ehrhardt (paelzer) wrote | #6 |
| description: | updated |
| Claudio Kuenzler (napsty) wrote | #7 |
| Robie Basak (racb) wrote | #8 |
| Christian Ehrhardt (paelzer) wrote | #9 |
| tags: | removed: server-triage-discuss |
| information type: | Public → Public Security |
| information type: | Public Security → Private Security |
| information type: | Private Security → Public |
Odd, this clearly works for me in a new system
# ll /run/haproxy
ls: cannot access '/run/haproxy': No such file or directory
root@b:~# apt install haproxy
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following package was automatically installed and is no longer required:
libfreetype6
Use 'apt autoremove' to remove it.
The following additional packages will be installed:
liblua5.3-0
Suggested packages:
vim-haproxy haproxy-doc
The following NEW packages will be installed:
haproxy liblua5.3-0
0 upgraded, 2 newly installed, 0 to remove and 9 not upgraded.
Need to get 1231 kB of archives.
After this operation, 2842 kB of additional disk space will be used.
Do you want to continue? [Y/n] Y
Get:1 http://
Get:2 http://
Fetched 1231 kB in 1s (2143 kB/s)
Selecting previously unselected package liblua5.3-0:amd64.
(Reading database ... 28651 files and directories currently installed.)
Preparing to unpack .../liblua5.
Unpacking liblua5.3-0:amd64 (5.3.3-
Selecting previously unselected package haproxy.
Preparing to unpack .../haproxy_
Unpacking haproxy (1.8.8-1ubuntu0.9) ...
Setting up liblua5.3-0:amd64 (5.3.3-
Setting up haproxy (1.8.8-1ubuntu0.9) ...
Created symlink /etc/systemd/
Processing triggers for libc-bin (2.27-3ubuntu1) ...
Processing triggers for systemd (237-3ubuntu10.31) ...
Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
Processing triggers for rsyslog (8.32.0-1ubuntu4) ...
Processing triggers for ureadahead (0.100.0-21) ...
root@b:~# ll /run/haproxy
total 0
drwxrwsr-x 2 haproxy haproxy 60 Dec 6 12:03 ./
drwxr-xr-x 19 root root 740 Dec 6 12:03 ../
srw-rw---- 1 root haproxy 0 Dec 6 12:03 admin.sock=
Directory is created on package install and the service running.
So it really comes down to /usr/lib/
There is much more than just haproxy in there, not being able to rely on it at all would totally disable that feature and all packages would need to be modified.
I don't think we'd do that but also have no perfect answer for you.
Personal opinion: if you want to use the container as a system-container instead of a microservice then use a proper system container service like LXD instead of docker.
I'll need to talk to a few people about that to gather more opinions about what we want to do for tmpfiles.d here.