[3.1][3.1+snap7] /proc/ not mounted
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu Image |
New
|
Undecided
|
Unassigned |
Bug Description
It appears as though the chroot cannot or does not mount /proc/ which is causing this error:
$ sudo ubuntu-image -v classic -w workdir/ -O output/ ubuntu-
[0] make_temporary_
[1] determine_
[2] build_gadget_tree
[3] prepare_gadget_tree
[4] load_gadget_yaml
[5] verify_
[6] germinate
[7] create_chroot
[8] install_packages
[9] prepare_image
Fetching firefox (3627)
Fetching gnome-42-2204 (143)
Fetching gtk-common-themes (1535)
Fetching snap-store (1047)
Fetching snapd-desktop-
Fetching core22 (1035)
Fetching bare (5)
Fetching snapd (20674)
[10] preseed_image
[11] clean_rootfs
[12] customize_
[13] customize_fstab
[14] perform_
Error: Error running script "/usr/sbin/chroot workdir/chroot /usr/sbin/
⚠️ /proc/ is not mounted. This is not a supported mode of operation. Please fix
your invocation environment to mount /proc/ and /sys/ properly. Proceeding anyway.
Your mileage may vary.
Created symlink /etc/systemd/
⚠️ /proc/ is not mounted. This is not a supported mode of operation. Please fix
your invocation environment to mount /proc/ and /sys/ properly. Proceeding anyway.
Your mileage may vary.
The unit files have no installation config (WantedBy=, RequiredBy=, Also=,
Alias= settings in the [Install] section, and DefaultInstance= for template
units). This means they are not meant to be enabled or disabled using systemctl.
Possible reasons for having this kind of units are:
• A unit may be statically enabled by being symlinked from another unit's
.wants/ or .requires/ directory.
• A unit's purpose may be to act as a helper for some other unit which has
a requirement dependency on it.
• A unit may be started when needed via activation (socket, path, timer,
D-Bus, udev, scripted systemctl call, ...).
• In case of template units, the unit is meant to be enabled with some
instance name specified.
⚠️ /proc/ is not mounted. This is not a supported mode of operation. Please fix
your invocation environment to mount /proc/ and /sys/ properly. Proceeding anyway.
Your mileage may vary.
Created symlink /etc/systemd/
sudo: unknown user oem
sudo: error initializing audit plugin sudoers_audit
I can reproduce this after building the snap based on the 3.0 tag upstream, in addition to the latest stable channel.