New issue
Advanced search Search tips

Issue 871922 link

Starred by 5 users

Issue metadata

Status: Available
Owner: ----
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug


Show other hotlists

Hotlists containing this issue:
LXD


Sign in to add a comment

snaps do not work in the Linux (Beta) Environment of Crostini

Project Member Reported by antiabong@google.com, Aug 7

Issue description

Chrome version: 69.0.3497.21 (Official Build) dev (64-bit)
OS: Chrome

Repro steps:
1. snap install <any app>
2. 
3. 

Expected: 
snap install <anyapp e.g remmina>
2018-08-07T19:58:50Z INFO Waiting for restart...
2018-08-07T19:58:56Z INFO snap "remmina" has bad plugs or slots: desktop, desktop-legacy, wayland (unknown interface)
remmina 1.2.31.2 from 'remmina' installed
root@ekun1:/usr/local/google/home/antiabong#


Actual: 
error: cannot perform the following tasks:
- Mount snap "core" (5145) ([start snap-core-5145.mount] failed with exit status 1: Job for snap-core-5145.mount failed.
See "systemctl status snap-core-5145.mount" and "journalctl -xe" for details.




root@penguin:/home/antiabong# systemctl status snap-core-5145.mount
● snap-core-5145.mount - Mount unit for core
   Loaded: loaded (/etc/systemd/system/snap-core-5145.mount; enabled; vendor preset: enabled
   Active: failed (Result: exit-code) since Tue 2018-08-07 19:44:51 UTC; 29min ago
    Where: /snap/core/5145
     What: /var/lib/snapd/snaps/core_5145.snap
  Process: 7210 ExecMount=/bin/mount /var/lib/snapd/snaps/core_5145.snap /snap/core/5145 -t 
      CPU: 4ms

Aug 07 19:44:51 penguin systemd[1]: snap-core-5145.mount: Failed to reset devices.list: Oper
Aug 07 19:44:51 penguin systemd[1]: snap-core-5145.mount: Failed to set invocation ID on con
Aug 07 19:44:51 penguin systemd[1]: Mounting Mount unit for core...
Aug 07 19:44:51 penguin systemd[1]: snap-core-5145.mount: Mount process exited, code=exited 
Aug 07 19:44:51 penguin systemd[1]: Failed to mount Mount unit for core.
Aug 07 19:44:51 penguin systemd[1]: snap-core-5145.mount: Unit entered failed state.







Aug 07 19:44:51 penguin /usr/lib/snapd/snapd[54]: task.go:303: DEBUG: 2018-08-07T19:44:51Z E
                                                  See "systemctl status snap-core-5145.mount
Aug 07 19:44:51 penguin systemd[1]: Failed to mount Mount unit for core.
-- Subject: Unit snap-core-5145.mount has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit snap-core-5145.mount has failed.
-- 
-- The result is failed.
Aug 07 19:44:51 penguin systemd[1]: snap-core-5145.mount: Unit entered failed state.
Aug 07 19:44:51 penguin /usr/lib/snapd/snapd[54]: taskrunner.go:353: DEBUG: Running task 201
Aug 07 19:44:51 penguin systemd[1]: Started Daily apt download activities.
-- Subject: Unit apt-daily.service has finished start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit apt-daily.service has finished starting up.
-- 
-- The start-up result is done.
Aug 07 19:44:51 penguin systemd[1]: apt-daily.timer: Adding 3h 13min 9.681422s random time.
Aug 07 19:44:51 penguin systemd[1]: apt-daily.timer: Adding 10h 46min 59.765625s random time











 
Components: OS>Systems>Containers
Labels: -Pri-2 Pri-3
i don't think we're looking at snap support currently, although we will at some point
Status: Available (was: Untriaged)
This can basically be fixed by running a kernel that allows FUSE mounts in user namespaces which is something that we recently merged and is available upstream from 4.18 kernels onwards ( https://lwn.net/Articles/755498/ ). Then the only thing left to do is to install squashfuse before installing the snap. That's it.

Sign in to add a comment