<div dir="ltr"><div class="gmail_quote"><div dir="ltr"><div dir="ltr"><div class="gmail_quote">I am encountering a strange problem with Nested LXD on AWS EC2 Ubuntu 18.04 instances...</div><div class="gmail_quote"><br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><b>snap 2.37.4<br>snapd 2.37.4<br>series 16<br>ubuntu 18.04<br>kernel 4.15.0-46-generic<br>LXD 3.11</b></blockquote></div><div class="gmail_quote"><br></div><div class="gmail_quote">In my AWS 18.04 host I install SNAP LXD and create an Ubuntu 18.04 container lets call <b>"parent"</b><br></div><div class="gmail_quote"><br></div><div class="gmail_quote">I enable Nesting for <b>"parent"</b></div><div class="gmail_quote"><br></div><div class="gmail_quote">I enter "parent" and apt-get update, apt-get upgrade ... no problem</div><div class="gmail_quote"><br></div><div class="gmail_quote">In "parent" I also install SNAP LXD and create an Ubuntu 18.04 container lets call <b>"child"</b></div><div class="gmail_quote"><br></div><div class="gmail_quote">I enter "child" and when I try to "<b>apt-get update, apt-get upgrade</b>" ... I see the very <u>same</u> packages to be upgraded</div><div class="gmail_quote">as I did when I upgrade "<b>parent</b>" ... however in <b>"child"</b> I get errors related to apport, udev ??</div><div class="gmail_quote"><br></div><div class="gmail_quote">I also see failure messages related to systemd-networkd.service access denied etc (see below)</div><div class="gmail_quote"><br></div><div class="gmail_quote">Note: I tried this on a local KVM Ubuntu 18.04 VM<br><br><div dir="ltr"><div dir="ltr"><div dir="ltr"><div class="gmail_quote"><div dir="ltr"><div dir="ltr"><div class="gmail_quote"><div dir="ltr" class="gmail_attr"><b>These are some of the packages that would be updated/upgraded in BOTH the "parent" and "child" Ubuntu 18.04 container on an AWS EC2 Ubuntu Bionic instance:</b><br></div><br><div dir="ltr"><div dir="ltr"><div>The following package was automatically installed and is no longer required:</div><div> libfreetype6</div><div>Use 'apt autoremove' to remove it.</div><div>The following packages will be upgraded:</div><div> <b>apport</b> libnss-systemd libpam-modules libpam-modules-bin libpam-runtime libpam-systemd libpam0g libseccomp2 libsystemd0 libudev1</div><div> libxcb1 python3-apport python3-problem-report snapd systemd systemd-sysv<b> udev</b></div><div>17 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.</div><div>Need to get 19.9 MB of archives.</div><div>After this operation, 49.2 kB of additional disk space will be used.</div><div>Do you want to continue? [Y/n] </div><div><br></div><div><b>Here are some of the errors that result...</b><br></div><div><br></div><div><div>(Reading database ... 28595 files and directories currently installed.)</div><div>Preparing to unpack .../libpam-runtime_1.1.8-3.6ubuntu2.18.04.1_all.deb ...</div><div>Unpacking libpam-runtime (1.1.8-3.6ubuntu2.18.04.1) over (1.1.8-3.6ubuntu2) ...</div><div>Setting up libpam-runtime (1.1.8-3.6ubuntu2.18.04.1) ...</div><div>Setting up systemd (237-3ubuntu10.15) ...</div><div><b>Failed to try-restart systemd-networkd.service: Access denied</b></div><div>See system logs and 'systemctl status systemd-networkd.service' for details.</div><div><b>Failed to try-restart systemd-resolved.service: Access denied</b></div><div>See system logs and 'systemctl status systemd-resolved.service' for details.</div><div><b>Failed to try-restart systemd-timesyncd.service: Access denied</b></div><div>See system logs and 'systemctl status systemd-timesyncd.service' for details.</div><div><b>Failed to try-restart systemd-journald.service: Access denied</b></div><div>See system logs and 'systemctl status systemd-journald.service' for details.</div><div>(Reading database ... 28595 files and directories currently installed.)</div><div>Preparing to unpack .../systemd-sysv_237-3ubuntu10.15_amd64.deb ...</div><div>Unpacking systemd-sysv (237-3ubuntu10.15) over (237-3ubuntu10.13) ...</div><div>Preparing to unpack .../libseccomp2_2.3.1-2.1ubuntu4.1_amd64.deb ...</div><div>Unpacking libseccomp2:amd64 (2.3.1-2.1ubuntu4.1) over (2.3.1-2.1ubuntu4) ...</div><div>Setting up libseccomp2:amd64 (2.3.1-2.1ubuntu4.1) ...</div><div>(Reading database ... 28595 files and directories currently installed.)</div><div>Preparing to unpack .../libxcb1_1.13-2~ubuntu18.04_amd64.deb ...</div><div>Unpacking libxcb1:amd64 (1.13-2~ubuntu18.04) over (1.13-1) ...</div><div>Preparing to unpack .../python3-problem-report_2.20.9-0ubuntu7.6_all.deb ...</div><div>Unpacking python3-problem-report (2.20.9-0ubuntu7.6) over (2.20.9-0ubuntu7.5) ...</div><div>Preparing to unpack .../python3-apport_2.20.9-0ubuntu7.6_all.deb ...</div><div>Unpacking python3-apport (2.20.9-0ubuntu7.6) over (2.20.9-0ubuntu7.5) ...</div><div>Preparing to unpack .../apport_2.20.9-0ubuntu7.6_all.deb ...</div><div><b>Failed to retrieve unit state: Access denied</b></div><div><b>invoke-rc.d: could not determine current runlevel</b></div><div><b>Failed to reload daemon: Access denied</b></div><div><br></div></div><div><b>So I interrupted the script that was doing the above attempt at apt update && apt upgrade -y </b></div><div><b>and opened a terminal and t</b><b>hen.. and tried this:</b></div><div><b><br></b></div><div>lxc exec test bash<br></div><div>apt update && apt upgrade </div><div><br></div><div>But of course because i'd interrupted the above apt upgrade I had to do <b>dpkg --configure -a</b></div><div><br></div><div><div><b>dpkg --configure -a</b></div><div>Setting up libnss-systemd:amd64 (237-3ubuntu10.15) ...</div><div>Processing triggers for ureadahead (0.100.0-20) ...</div><div>Setting up systemd-sysv (237-3ubuntu10.15) ...</div><div>Setting up python3-problem-report (2.20.9-0ubuntu7.6) ...</div><div>Processing triggers for libc-bin (2.27-3ubuntu1) ...</div><div>Setting up udev (237-3ubuntu10.15) ...</div><div><b>Failed to reload daemon: Access denied</b></div><div>dpkg: error processing package udev (--configure):</div><div> installed udev package post-installation script subprocess was interrupted</div><div>Processing triggers for man-db (2.8.3-2ubuntu0.1) ...</div><div>Processing triggers for dbus (1.12.2-1ubuntu1) ...</div><div><b>Failed to open connection to "system" message bus: Failed to query AppArmor policy: Permission denied</b></div><div>Setting up libxcb1:amd64 (1.13-2~ubuntu18.04) ...</div><div>Setting up libpam-systemd:amd64 (237-3ubuntu10.15) ...</div><div>Setting up python3-apport (2.20.9-0ubuntu7.6) ...</div><div>dpkg: error processing package apport (--configure):</div><div> package is in a very bad inconsistent state; you should</div><div> reinstall it before attempting configuration</div><div>Processing triggers for libc-bin (2.27-3ubuntu1) ...</div><div><b>Errors were encountered while processing:</b></div><div><b> udev</b></div><div><b> apport</b></div></div><div><br></div><div><b>I went back and tried to reinstall apport...</b></div><div><br></div><div><div># apt install --reinstall apport</div><div>Reading package lists... Done</div><div>Building dependency tree </div><div>Reading state information... Done</div><div>The following package was automatically installed and is no longer required:</div><div> libfreetype6</div><div>Use 'apt autoremove' to remove it.</div><div>Suggested packages:</div><div> apport-gtk | apport-kde</div><div>The following packages will be upgraded:</div><div> apport</div><div>1 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.</div><div>2 not fully installed or removed.</div><div>Need to get 0 B/124 kB of archives.</div><div>After this operation, 0 B of additional disk space will be used.</div><div>(Reading database ... 28595 files and directories currently installed.)</div><div>Preparing to unpack .../apport_2.20.9-0ubuntu7.6_all.deb ...</div><div><b>Failed to retrieve unit state: Access denied</b></div><div><b>invoke-rc.d: could not determine current runlevel</b></div><div><b>Failed to reload daemon: Access denied</b></div><div><br></div></div><div>======================================</div><div><br></div><div>Does anyone have any idea what might be causing this? </div><div>Again this is happening on AWS and on a local KVM Ubuntu VM.</div><div><br></div><div>Thanks for any ideas or suggestions.</div><div><br></div><div>Brian</div><div><br></div></div></div>
</div></div></div>
</div></div></div></div>
</div></div></div>
</div></div>