** Merge proposal linked:
https://code.launchpad.net/~ahasenack/ubuntu/+source/samba/+git/samba/+merge/470654
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2046486
** Merge proposal unlinked:
https://code.launchpad.net/~ahasenack/ubuntu/+source/samba/+git/samba/+merge/470654
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2046486
** Merge proposal linked:
https://code.launchpad.net/~ahasenack/ubuntu/+source/samba/+git/samba/+merge/470654
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2046486
Apparmor fixes for running Oracular unprivileged containers from
`ubuntu-daily:24.10` are being progressively rolled out to the
`latest/stable` channel now.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Oracular unprivileged containers should now be working OK in
latest/candidate channel.
In latest/edge and latest/candidate we have added a vendored version of
the apparmor parser (v4.0.2).
If our tests pass OK then will proceed to deploy latest/candidate to
latest/stable on Monday.
--
You
OK excellent, so as discussed we'll need to vendor the upstream version
of apparmor into the LXD snap (so we don't have to prematurely rush the
core24 switch) along with the cherry-picks you identified in the GH
issue.
I'll work on landing that in latest/edge first and then we can perform
an
>Ill need to check with mihalicyn if the fix relies on a thr lxd snap
switching base to core24.
no, but we need https://github.com/canonical/lxd-pkg-snap/pull/477
Full details:
https://github.com/canonical/lxd/issues/13810#issuecomment-2253259452
--
You received this bug notification because
As for when it hits stable channels, im assuming the most important ones
are latest/stable and 5.21/stable (which is the current lts series).
Ill need to check with mihalicyn if the fix relies on a thr lxd snap
switching base to core24.
If so we've got some more issues to resolve first, but if
I mention it only for the purposes of testing and for keeping this
ticket informed, i was not suggesting you run production on latest/edge
naturally.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
latest/edge is not what we use (nor what we should use) in production.
When should we expect this to reach the default stable channels used on
Ubuntu LTSes?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
This is fixed now in latest/edge of lxd for unprivileged containers.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2046486
Title:
units with credentials fail in LXD
see also
https://github.com/canonical/lxd/issues/13810
** Changed in: lxd (Ubuntu)
Status: Confirmed => Fix Committed
** Bug watch added: github.com/canonical/lxd/issues #13810
https://github.com/canonical/lxd/issues/13810
--
You received this bug notification because you are a
https://github.com/canonical/lxd/pull/13820
** Changed in: lxd (Ubuntu)
Assignee: (unassigned) => Aleksandr Mikhalitsyn (mihalicyn)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
blech, sorry, misclicks trying to get things added properly
marking as affects cloud-images as producers of the lxd images.
** Also affects: systemd
Importance: Undecided
Status: New
** No longer affects: systemd
** Also affects: cloud-images
Importance: Undecided
Status:
14 matches
Mail list logo
