That's entirely fair, but in that case isn't going snap-only for "chromium-browser" a bit short-sighted, given the constraints on running snaps?
-- 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 in docker Status in cloud-images: Incomplete Status in chromium-browser package in Ubuntu: Invalid Status in snapd package in Ubuntu: Invalid 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 : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
