I agree this would just end up in messy workarounds. I see the main
culprit in the snap daemon. I don't see a chance, that Ubuntu will
switch back from snap to plain deb for this package because it fixes
only this 1 snap. A fundamental solution would be to make snaps work in
general for containerized applications. However, I have no clue, what
the daemon does and if it can be made optional for containers.
** Also affects: snapd (Ubuntu)
Importance: Undecided
Status: New
--
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/1869963
Title:
Unable to install chromium-browser 20.04
Status in cloud-images:
Incomplete
Status in chromium-browser package in Ubuntu:
Invalid
Status in snapd package in Ubuntu:
New
Bug description:
Steps to reproduce: Create a docker container with the official image
"ubuntu:focal". Inside of the container, run "apt-get install
chromium-browser".
Expected results: Chromium is installed.
Actual results: Chromium installation fails. The error is telling me
that it is unable to reach the snap store (probably because snapd is
not running).
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1869963/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
