Tor relay stopped working on Ubuntu 18.04 in LXD container after update to 0.4.2.5-1~bionic+1

LXD
,
1

I am running a tor relay on Ubuntu 18.04 in a LXD container (installed with Snap, version 3.18, rev 12631). After upgrading form tor from version 0.4.1.6-1~bionic+1 to version 0.4.2.5-1~bionic+1, it stopped working.

Here what I have in /var/log/syslog

Dec 23 13:22:29 tor systemd[1]: tor@default.service: Failed to reset devices.list: Operation not permitted
Dec 23 13:22:29 tor systemd[1]: Failed to set devices.allow on /system.slice/system-tor.slice/tor@default.service: Operation not permitted
Dec 23 13:22:29 tor systemd[1]: message repeated 2 times: [ Failed to set devices.allow on /system.slice/system-tor.slice/tor@default.service: Operation not permitted]
Dec 23 13:22:29 tor tor[5887]: Dec 23 13:22:29.582 [notice] Tor 0.4.2.5 running on Linux with Libevent 2.1.8-stable, OpenSSL 1.1.1, Zlib 1.2.11, Liblzma 5.2.2, and Libzstd 1.3.3.
Dec 23 13:22:29 tor tor[5887]:
Dec 23 13:22:29.582 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
Dec 23 13:22:29 tor tor[5887]: Dec 23 13:22:29.582 [notice] Read configuration file "/usr/share/tor/tor-service-defaults-torrc".
Dec 23 13:22:29 tor tor[5887]: Dec 23 13:22:29.582 [notice] Read configuration file "/etc/tor/torrc".
Dec 23 13:22:29 tor tor[5887]:
Dec 23 13:22:29.583 [notice] Based on detected system memory, MaxMemInQueues is set to 6260 MB. You can override this by setting MaxMemInQueues by hand.
Dec 23 13:22:29 tor tor[5887]: Dec 23 13:22:29.584 [warn] ControlPort is open, but no authentication method has been configured.  This means that any program on your computer can reconfigure your Tor.  That's bad!  You should upgrade your Tor controller as soon as possible.
Dec 23 13:22:29 tor systemd[1]: Failed to set devices.allow on /system.slice/system-tor.slice/tor@default.service: Operation not permitted
Dec 23 13:22:29 tor tor[5887]: Configuration was valid

I asked in different places. Since noone seems to understand what’s going on and noone encounter the same issue, I start to think that this is something specific to LXD.

2

There are no actual errors in the output you’re showing above, everything in there are warnings or notices which should not prevent the service from starting.