[pkg-lxc-devel] Bug#1111087: transmission-daemon: Service does not start inside a container (code=exited, status=226/NAMESPACE)

[Elena ``of Valhalla'']

On 2025-08-15 at 09:30:41 +0200, Alexandre Rossi wrote:
> I suggest you try to remove hardening options in transmission-daemon.service
> using:
> 
>     # systemctl edit transmission-daemon.service
> 
> and see how it goes, and please report here.

I tried, and indeed transmission-daemon does work this way

I guess it will have to do as a workaround

> > If the problem is that I'm missing some extra configuration because of
> > the container situation, would it be possible to document it in a
> > README.Debian in the usual place, please?
> 
> I have not used lxc for more than a decade, so not really knowledgeable on
> these problems. From other similar bug report discussions I could find,
> this may be a lxc bug (not supporting systemd hardening options) or a
> misconfiguration of the lxc container by the administrator. Looking at
> the lxc bug page[1], there are many similar reports.

I'll reassign the bug to lxc, then, and hope for the best

(the lxc container used basically the default configuration, I only had
to add a network interface)

> I'm ok to include some hints in README.Debian if you can provide those.

sadly my expertees in next to nothing (up to now everything had just
worked — thanks to all of the work of the Debian people involved), but
if I'll get anything from elsewhere I'll let you know.

-- 
Elena ``of Valhalla''