** Tags added: id-5d9f086c55aa263ba7e2f5e5
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1844498
Title:
18.10+ cloud images have the LXD group as gid 1000
To manage notifications about this bug go
Closing the ubuntu snapd task as this bug is already on the project
snapd
** Changed in: snapd
Status: New => In Progress
** Changed in: snapd (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
If snapd should change for this I think we need to have some design to
discuss how this should look. AIUI there is a desire to express that
some snaps needs groups created on the host (like lxd) when a snap gets
installed. We could make this work, but even then with our current model
where snaps
** Also affects: snapd
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1844498
Title:
18.10+ cloud images have the LXD group as gid 1000
To manage
> core20 snap builds started to fail now, as it installs a
> few more packages on top of base, and expects to maintain stable gids
In principle, the snap build should follow the changes in behavior in
livecd-rootfs, rather than blocking us from making any changes; it's a
sanity check against
On Thu, 10 Oct 2019, 23:41 Dimitri John Ledkov,
wrote:
> This has now added
> lxd:x:101:
>
> Into ubuntu-base tarballs http://cdimage.ubuntu.com/ubuntu-
> base/daily/pending/ which is a bit problematic.
>
> Was that intended?
>
I think it was sort of known, vs actively intended.
core20 snap
note that the build scripts for core do have an md5sum check to detect changes
to /etc/passwd|group|shadow because this file is orignally readonly.
dirs created with specific UIDs/GIDs by package postinist scripts that get
copied into the writable area of the rootfs during first boot would fail
This has now added
lxd:x:101:
Into ubuntu-base tarballs http://cdimage.ubuntu.com/ubuntu-
base/daily/pending/ which is a bit problematic.
Was that intended?
core20 snap builds started to fail now, as it installs a few more
packages on top of base, and expects to maintain stable gids
Currently
https://travis-
ci.org/snapcore/core20/builds/596036023?utm_source=github_status_medium=notification
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1844498
Title:
18.10+ cloud images have the LXD
This bug was fixed in the package livecd-rootfs - 2.618
---
livecd-rootfs (2.618) eoan; urgency=medium
[ Michael Hudson-Doyle ]
* Do not create a hook manually for ubuntu-cpc builds, make-hooks does not
like that.
-- Steve Langasek Tue, 08 Oct 2019
21:21:45 -0700
**
** Merge proposal linked:
https://code.launchpad.net/~mwhudson/livecd-rootfs/+git/livecd-rootfs/+merge/373845
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1844498
Title:
18.10+ cloud images
https://code.launchpad.net/~mwhudson/livecd-rootfs/+git/livecd-
rootfs/+merge/373789
** Changed in: livecd-rootfs (Ubuntu)
Status: New => In Progress
** Changed in: livecd-rootfs (Ubuntu)
Assignee: (unassigned) => Michael Hudson-Doyle (mwhudson)
--
You received this bug
Per Steve's comment, I'm going to move the cloud-init task to Invalid.
I don't fully understand the "extensions" referenced in comment #5, but
it seems clear to me that they should be tracked in a separate bug.
I'll let someone who _does_ understand that ask file that bug. :)
** Changed in:
On Thu, Sep 26, 2019 at 05:27:22PM -, Michael Vogt wrote:
> I wonder if adding something to cloud.cfg that ensures there is a lxd
> group created as a system-group would be the way forward? Especially
> since we already reference this group in cloud.cfg.
For the specific case of a preseeded
I wonder if adding something to cloud.cfg that ensures there is a lxd
group created as a system-group would be the way forward? Especially
since we already reference this group in cloud.cfg.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This is complicated.
The root cause, I believe, is lxd moving from a deb (which created the
lxd system group when installed during image build) to a snap (which
creates the group after/during first boot but, crucially, after cloud-
init has created users and therefore the lxd group itself). As a
I don't love the idea of two passes on adding users/groups.
https://stackoverflow.com/questions/57605982/how-to-make-a-custom-gid-in-groupadd-cloud-init
has an idea for another solution. sort of.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Tags added: id-5d84bb1ca26b0679a708dc40
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1844498
Title:
18.10+ cloud images have the LXD group as gid 1000
To manage notifications about this bug go
I have added two other packages to this bug.
livecd-rootfs - For the ubuntu-server and ubuntu-cpc projects a chroot
hook should be added to create the lxd system group.
cloud-init - We have the suggestion that user creation should not
initially create user groups that do not exist. You may
19 matches
Mail list logo
