This is not a container, this is the desktop installer iso system. Yes, "snap list" returns something in the installer system but it is run in the chrooted env. "chroot /target snap list" is working too. It should not, is it right ?
As said in the previous issue, i want those snap to be installed after the first boot. I don't have any connectivity issue, the same ansible playbook installs many apt packages. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1927071 Title: Fresh install of chromium-browser during installer-like process, in a chroot fails (when preparing machines prior to first boot) Status in chromium-browser package in Ubuntu: Incomplete Bug description: Here is the first bug report : https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/1882232 It seems that there is a regression, pre-installation script of apt installed chromium-browser package doesn't detect that it is running in a chroot anymore. => Installing the chromium snap ==> Checking connectivity with the snap store ===> Unable to contact the store, trying every minute for the next 30 minutes ===> Still unable to contact the store, trying for another 20 minutes ===> Still unable to contact the store, trying for another 10 minutes ===> Still unable to contact the store, aborting dpkg: error processing archive /var/cache/apt/archives/chromium-browser_1%3a85.0.4183.83-0ubuntu0.20.04.2_amd64.deb (--unpack): new chromium-browser package pre-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1927071/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
