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

[Nick Rosbrook]

Is this still an issue? I tried running a bionic LXD container from a
Lunar host, and in the container I was able to run the snap without
issues.

** Changed in: systemd (Ubuntu)
       Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, 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 Snappy:
  New
Status in systemd package in Ubuntu:
  Incomplete

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 at 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/snappy/+bug/1965328/+subscriptions