install chromium in lxc container for 20.04 fails

Bug #1889318 reported by Mike Bernson
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
snapd (Ubuntu)
Triaged
Medium
Unassigned

Bug Description

when trying to install chromium in 20.04 in a lxc container to fails to install with the following:
root@python:~# apt-get install chromium-browser
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
  libfuse2 snapd squashfs-tools
Suggested packages:
  fuse zenity | kdialog
The following NEW packages will be installed:
  chromium-browser libfuse2 snapd squashfs-tools
0 upgraded, 4 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/27.5 MB of archives.
After this operation, 121 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Preconfiguring packages ...
Selecting previously unselected package squashfs-tools.
(Reading database ... 100799 files and directories currently installed.)
Preparing to unpack .../squashfs-tools_1%3a4.4-1_amd64.deb ...
Unpacking squashfs-tools (1:4.4-1) ...
Selecting previously unselected package libfuse2:amd64.
Preparing to unpack .../libfuse2_2.9.9-3_amd64.deb ...
Unpacking libfuse2:amd64 (2.9.9-3) ...
Selecting previously unselected package snapd.
Preparing to unpack .../snapd_2.45.1+20.04.2_amd64.deb ...
Unpacking snapd (2.45.1+20.04.2) ...
Setting up squashfs-tools (1:4.4-1) ...
Setting up libfuse2:amd64 (2.9.9-3) ...
Setting up snapd (2.45.1+20.04.2) ...
Cache read/write disabled: interface file missing. (Kernel needs AppArmor 2.4 compatibility patch.)
Warning: unable to find a suitable fs in /proc/mounts, is it mounted?
Use --subdomainfs to override.
snapd.failure.service is a disabled or a static unit, not starting it.
snapd.snap-repair.service is a disabled or a static unit, not starting it.
(Reading database ... 100896 files and directories currently installed.)
Preparing to unpack .../chromium-browser_83.0.4103.97-0ubuntu0.20.04.1_amd64.deb ...
=> Installing the chromium snap
==> Checking connectivity with the snap store
==> Installing the chromium snap
error: system does not fully support snapd: apparmor detected but insufficient
       permissions to use it
dpkg: error processing archive /var/cache/apt/archives/chromium-browser_83.0.4103.97-0ubuntu0.20.04.1_amd64.deb (--unpack):
 new chromium-browser package pre-installation script subprocess returned error exit status 1
Errors were encountered while processing:
 /var/cache/apt/archives/chromium-browser_83.0.4103.97-0ubuntu0.20.04.1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@python:~#

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: chromium-browser (not installed)
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
CasperMD5CheckResult: skip
Date: Tue Jul 28 18:14:27 2020
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: chromium-browser
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Mike Bernson (mike-mlb) wrote :
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your bug report, that's a snapd issue, sounds similar to bug #1865503

affects: chromium-browser (Ubuntu) → snapd (Ubuntu)
Revision history for this message
Mike Bernson (mike-mlb) wrote :

This might have the same root cause but 1865503 is using LXD where I had the problem using
lxc (lxc-start).

Once fixed need to make sure the fix work under lxc (lxc-start) also.

Changed in snapd (Ubuntu):
importance: Undecided → Medium
Changed in snapd (Ubuntu):
status: New → Triaged
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.