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
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to 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)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1927071/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
