← Back to team overview

debcrafters-packages team mailing list archive

[Bug 1965328] Re: transient scope could not be started error in bionic lxd container

 

FYI seeing this one again:

arch: s390x
host release: noble
lxd: installed:          6.3-a85d6a5               (33245) 104MB -
snapd: installed:          2.68.4                       (24506) 48MB snapd

$ lxd stop testkvm-focal-to
internal error, please report: running "lxd" failed: transient scope could not be started, job /org/freedesktop/systemd1/job/5146 finished with result failed

-- 
You received this bug notification because you are a member of
Debcrafters packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1965328

Title:
  transient scope could not be started error in bionic lxd container

Status in snapd:
  New
Status in systemd package in Ubuntu:
  Invalid
Status in systemd source package in Bionic:
  New

Bug description:
  On my impish development host machine I tend to use lxd containers to
  support snap building and other tasks targeting different releases.
  Today I came to use a bionic container as per usual and found that I
  could not invoke any snap applications. I installed hello-world as the
  most simple test of running a snap app:

  ```
  ubuntu@b:~$ hello-world
  internal error, please report: running "hello-world" failed: transient scope could not be started, job /org/freedesktop/systemd1/job/44 finished with result failed
  ```

  I made sure the container had up to date packages in it (apt & snaps)
  and rebooted it. But the problem persisted. I then created a second
  container and installed hello-world in it and again the problem was
  reproducible. At the time of producing the following attachments I had
  not attempted to reboot the host.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1965328/+subscriptions