Fresh install of chromium-browser during installer-like process, in a chroot fails (when preparing machines prior to first boot)

Bug #1927071 reported by eoli3n on 2021-05-04

This bug report will be marked for expiration in 49 days if no further activity occurs. (find out why)

6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
chromium-browser (Ubuntu)
Undecided
Unassigned

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

eoli3n (eoli3neoli3n) wrote :
Olivier Tilloy (osomon) wrote :

That looks like a slightly different issue: the preinst script is detecting that snapd is usable by checking for the existence of /run/snapd.socket in the container/chroot. In your case it appears that the socket exists, meaning that snapd is installed and running. But it fails to contact the snap store. Does your container have access to internet? Can you check whether snapd actually works in that container setup (run e.g. `snap list`)?

Changed in chromium-browser (Ubuntu):
status: New → Incomplete
eoli3n (eoli3neoli3n) wrote :

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.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Bug attachments