Lxd: Mount snap "core" (1689) ([start snap-core-1689.mount] failed with exit status 1
How to test snaps with LXD?
$ lxc launch ubuntu:16.04/amd64 snapsnap
$ lxc exec snapsnap -- snap install micro --beta
...
error: cannot perform the following tasks:
- Mount snap "core" (1689) ([start snap-core-1689.mount] failed with exit status 1: Job for snap-core-1689.mount failed. See "systemctl status snap-core-1689.mount" and "journalctl -xe" for details.
)
$ lxc exec snapsnap -- systemctl status snap-core-1689.mount
● snap-core-1689.mount - Mount unit for core
Loaded: loaded (/etc/systemd/system/snap-core-1689.mount; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Fri 2017-06-16 12:02:20 UTC; 6min ago
Where: /snap/core/1689
What: /var/lib/snapd/snaps/core_1689.snap
Process: 521 ExecMount=/bin/mount /var/lib/snapd/snaps/core_1689.snap /snap/core/1689 -t squashfs -o nodev,ro (code=exited, status=32)
Jun 16 12:02:20 snapsnap systemd[1]: Mounting Mount unit for core...
Jun 16 12:02:20 snapsnap mount[521]: mount: /snap/core/1689: mount failed: Unknown error -1
Jun 16 12:02:20 snapsnap systemd[1]: snap-core-1689.mount: Mount process exited, code=exited status=32
Jun 16 12:02:20 snapsnap systemd[1]: Failed to mount Mount unit for core.
Jun 16 12:02:20 snapsnap systemd[1]: snap-core-1689.mount: Unit entered failed state.
$ lxc exec snapsnap -- journalctl -xe
...
Jun 16 12:01:03 snapsnap snapd[337]: 2017/06/16 12:01:03.790126 api.go:912: Installing snap "micro" revision unset
Jun 16 12:01:04 snapsnap /usr/lib/snapd/snapd[337]: daemon.go:176: DEBUG: uid=0;@ POST /v2/snaps/micro 568.833648ms 202
Jun 16 12:01:04 snapsnap /usr/lib/snapd/snapd[337]: snapmgr.go:496: DEBUG: Next refresh scheduled for 2017-06-16 20:57:17.719060486 +0000 UTC.
Jun 16 12:01:04 snapsnap /usr/lib/snapd/snapd[337]: taskrunner.go:367: DEBUG: Running task 2 on Do: Download snap "core" (1689) from channel "stable"
Jun 16 12:02:18 snapsnap /usr/lib/snapd/snapd[337]: taskrunner.go:367: DEBUG: Running task 3 on Do: Fetch and check assertions for snap "core" (1689)
Jun 16 12:02:20 snapsnap /usr/lib/snapd/snapd[337]: taskrunner.go:367: DEBUG: Running task 4 on Do: Mount snap "core" (1689)
Jun 16 12:02:20 snapsnap systemd[1]: Reloading.
Jun 16 12:02:20 snapsnap systemd[1]: apt-daily.timer: Adding 2h 4min 14.263669s random time.
Jun 16 12:02:20 snapsnap systemd[1]: Reloading.
Jun 16 12:02:20 snapsnap systemd[1]: apt-daily.timer: Adding 11h 26min 34.666378s random time.
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/snap-core-1689.mount: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Mounting Mount unit for core...
-- Subject: Unit snap-core-1689.mount has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit snap-core-1689.mount has begun starting up.
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /user.slice: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /init.scope: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/proc-meminfo.mount: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/-.mount: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/proc-diskstats.mount: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/rc-local.service: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/sys-kernel-debug.mount: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/lvm2-monitor.service: Operation not permitted
Jun 16 12:02:20 snapsnap mount[521]: mount: /snap/core/1689: mount failed: Unknown error -1
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/dev-tty.mount: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/dev-lxd.mount: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/dev-fuse.mount: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/networking.service: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/dev-net-tun.mount: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/systemd-logind.service: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/sys-kernel-debug-tracing.mount: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/dev-.lxd\x2dmounts.mount: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/snapd.service: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/proc-stat.mount: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/proc-sys-fs-binfmt_misc.mount: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/var-lib-lxcfs.mount: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/dev-ptmx.mount: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/systemd-journald.service: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/cloud-config.service: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/system-getty.slice: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/ssh.service: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/systemd-random-seed.service: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/systemd-journal-flush.service: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/systemd-tmpfiles-setup.service: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/polkitd.service: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/dev-null.mount: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/ufw.service: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/apparmor.service: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/proc-swaps.mount: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/mdadm.service: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/dev-zero.mount: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/cron.service: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/sys-fs-fuse-connections.mount: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/resolvconf.service: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/atd.service: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/console-getty.service: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/proc-cpuinfo.mount: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/systemd-udev-trigger.service: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/ondemand.service: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/dbus.service: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/cloud-init.service: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/cloud-final.service: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/cloud-init-local.service: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/proc-uptime.mount: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/dev-urandom.mount: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/rsyslog.service: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/systemd-user-sessions.service: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/systemd-udevd.service: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/systemd-update-utmp.service: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/irqbalance.service: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/unattended-upgrades.service: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/dev-random.mount: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/apport.service: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/lxd-containers.service: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/dev-mqueue.mount: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/dev-full.mount: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: Failed to reset devices.list on /system.slice/accounts-daemon.service: Operation not permitted
Jun 16 12:02:20 snapsnap systemd[1]: snap-core-1689.mount: Mount process exited, code=exited status=32
Jun 16 12:02:20 snapsnap systemd[1]: Failed to mount Mount unit for core.
-- Subject: Unit snap-core-1689.mount has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit snap-core-1689.mount has failed.
--
-- The result is failed.
Jun 16 12:02:20 snapsnap systemd[1]: snap-core-1689.mount: Unit entered failed state.
Jun 16 12:02:20 snapsnap /usr/lib/snapd/snapd[337]: task.go:303: DEBUG: 2017-06-16T12:02:20Z ERROR [start snap-core-1689.mount] failed with exit status 1: Job for snap-core-1689.mount failed. See "systemctl status snap-core-1689.mount" and "journalctl -xe" for details.
Jun 16 12:02:20 snapsnap /usr/lib/snapd/snapd[337]: taskrunner.go:367: DEBUG: Running task 2 on Undo: Download snap "core" (1689) from channel "stable"
Jun 16 12:02:21 snapsnap /usr/lib/snapd/snapd[337]: handlers.go:204: Reported install problem for "core" as a6e1f2fe-528b-11e7-a696-fa163ebeb28a OOPSID
Jun 16 12:02:21 snapsnap snapd[337]: 2017/06/16 12:02:21.626068 handlers.go:204: Reported install problem for "core" as a6e1f2fe-528b-11e7-a696-fa163ebeb28a OOPSID
Required information
- Distribution: Ubuntu 17.04
- The output of "lxc info" or if that fails:
driver: lxc
driver_version: 2.0.8
kernel: Linux
kernel_architecture: x86_64
kernel_version: 4.10.0-23-generic
server: lxd
server_pid: 2214
server_version: "2.12"
storage: dir
storage_version: "1"
Information to attach
- [ ] any relevant kernel output (dmesg)
- [ ] container log (lxc info NAME --show-log)
- [ ] main daemon log (/var/log/lxd.log)
- [ ] output of the client with --debug
- [ ] output of the daemon with --debug
techtonik
All 16 comments
Did you install "squashfuse" prior to installing your snap package?
stgraber
on 16 Jun 2017
It's a known issue with snapd inside containers and one which is tracked by the snapd people upstream.
stgraber
on 16 Jun 2017
stgraber
on 16 Jun 2017
There is no such package in Ubuntu 16.04
root@snapsnap:~# apt install squashfuse
...
E: Unable to locate package squashfuse
You may need to run "apt update" to update the package list.
stgraber
on 17 Jun 2017
Yes. After apt update squashfuse installe successfully. snap install micro --beta was ok too. Why ubuntu:16.04/amd64 comes not updated? I thought that these images are updated frequently.
techtonik
on 17 Jun 2017
The image is indeed updated every few weeks and the packages in the image are therefore up to date.
"apt update" doesn't update any actual package (that's what "apt upgrade" would do), instead it just updates the package index files which are used to look up packages.
Anyway, looks like things are working as is expected. Hopefully snapd will finally bundle squashfuse soon and then things will be even easier.
stgraber
on 17 Jun 2017
@stgraber the question is why ubuntu:16.04/amd64 comes with updated software but outdated indexes?
techtonik
on 17 Jun 2017
I'm not sure, my best guess is that since those index files expire pretty quickly and can be somewhat big, they may not be included in the image itself, instead relying on the user (or cloud-init) running the update.
stgraber
on 17 Jun 2017
How to find out the size of container? df seems to report params of the host system,
root@snapsnap:~# df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda5 79458176 53099752 22299136 71% /
none 492 0 492 0% /dev
udev 3801356 0 3801356 0% /dev/tty
tmpfs 100 0 100 0% /dev/lxd
tmpfs 100 0 100 0% /dev/.lxd-mounts
tmpfs 3828332 0 3828332 0% /dev/shm
tmpfs 3828332 8348 3819984 1% /run
tmpfs 5120 0 5120 0% /run/lock
tmpfs 3828332 0 3828332 0% /sys/fs/cgroup
After apt update:
root@snapsnap:~# df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda5 79458176 53260384 22138504 71% /
none 492 0 492 0% /dev
udev 3801356 0 3801356 0% /dev/tty
tmpfs 100 0 100 0% /dev/lxd
tmpfs 100 0 100 0% /dev/.lxd-mounts
tmpfs 3828332 0 3828332 0% /dev/shm
tmpfs 3828332 8348 3819984 1% /run
tmpfs 5120 0 5120 0% /run/lock
tmpfs 3828332 0 3828332 0% /sys/fs/cgroup
(22299136-22138504)/1024=156.87 Mb which seems to much, because image list:
| DESCRIPTION | ARCH | SIZE | UPLOAD DATE |
+---------------------------------------------+---------+----------+-------------------------------+
| ubuntu 16.04 LTS amd64 (release) (20170610) | x86_64 | 153.78MB | Jun 14, 2017 at 8:36pm (UTC) |
+---------------------------------------------+---------+----------+-------------------------------+
Only ZFS and LVM will report the container size properly in "df -h". For everything else, your best bet is likely "du -sch /var/lib/lxd/containers/NAME/rootfs" on the host...
stgraber
on 18 Jun 2017
Well, I'd expect "du -schx /" inside the container to give you the right number too.
stgraber
on 18 Jun 2017
👍1
# du -schx /
606M /
606M total
# apt update
...
# du -schx /
763M /
763M total
(763-606)/606=0.26 - 26% increase is not that much, and I guess that people who need extra small images are using https://developer.ubuntu.com/core anyway.
techtonik
on 18 Jun 2017
Yeah, anyway, we don't have any control on that. Those images are the same Ubuntu images used for all cloud instances, not special LXD ones.
stgraber
on 18 Jun 2017
I am having this same issue.
system info
host: ubuntu 16.04.4 x86_64
lxd: 3.0.0 snap
kernel: 4.13.0-39-generic (previously 4.4.0-119-generic)
steps to reproduce
lxc launch images:ubuntu/16.04 nextcloud
lxc exec nextcloud -- apt install snapd -y
lxc exec nextcloud -- apt install squashfuse -y
lxc exec nextcloud -- snap install nextcloud
i have also tried to set the following configs for my lxc container:
lxc config set nextcloud security.privileged true
lxc config set nextcloud security.nesting true
lxc config set nextcloud raw.apparmor "fstype=squashfs,"
but I am still getting the error
Mount snap "core" (4407) ([start snap-core-4407.mount] failed with exit status 1: Job for snap-core-4407.mount failed. See "systemctl status snap-core-4407.mount" and "journalctl -xe" for details.
logs
systemctl status snap-core-4407.mount
● snap-core-4407.mount
Loaded: not-found (Reason: No such file or directory)
Active: failed (Result: exit-code) since Mon 2018-04-23 16:49:35 UTC; 3min 15s ago
Apr 23 16:49:35 nextcloud1 systemd[1]: Mounting Mount unit for core...
Apr 23 16:49:35 nextcloud1 mount[329]: mount: wrong fs type, bad option, bad superblock on /var/lib/snapd/snaps/c
Apr 23 16:49:35 nextcloud1 mount[329]: missing codepage or helper program, or other error
Apr 23 16:49:35 nextcloud1 mount[329]: In some cases useful info is found in syslog - try
Apr 23 16:49:35 nextcloud1 mount[329]: dmesg | tail or so.
Apr 23 16:49:35 nextcloud1 systemd[1]: snap-core-4407.mount: Mount process exited, code=exited status=32
Apr 23 16:49:35 nextcloud1 systemd[1]: Failed to mount Mount unit for core.
Apr 23 16:49:35 nextcloud1 systemd[1]: snap-core-4407.mount: Unit entered failed state.
journalctl -xe
Apr 23 16:49:24 nextcloud1 snapd[136]: 2018/04/23 16:49:24.352938 api.go:1004: Installing snap "nextcloud" revision unset
Apr 23 16:49:35 nextcloud1 systemd[1]: Reloading.
Apr 23 16:49:35 nextcloud1 systemd[1]: Reloading.
Apr 23 16:49:35 nextcloud1 systemd[1]: snap.mount: Directory /snap to mount over is not empty, mounting anyway.
-- Subject: Mount point is not empty
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- The directory /snap is specified as the mount point (second field in
-- /etc/fstab or Where= field in systemd unit file) and is not empty.
-- This does not interfere with mounting, but the pre-exisiting files in
-- this directory become inaccessible. To see those over-mounted files,
-- please manually mount the underlying file system to a secondary
-- location.
Apr 23 16:49:35 nextcloud1 systemd[1]: Failed to reset devices.list on /system.slice/snap.mount: Operation not permitted
Apr 23 16:49:35 nextcloud1 systemd[1]: Mounting Ensure that the snap directory shares mount events....
-- Subject: Unit snap.mount has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit snap.mount has begun starting up.
Apr 23 16:49:35 nextcloud1 systemd[1]: Failed to reset devices.list on /init.scope: Operation not permitted
Apr 23 16:49:35 nextcloud1 systemd[1]: Failed to reset devices.list on /system.slice/dev-.lxd\x2dmounts.mount: Operation not permitted
Apr 23 16:49:35 nextcloud1 systemd[1]: Failed to reset devices.list on /system.slice/sys-kernel-debug.mount: Operation not permitted
Apr 23 16:49:35 nextcloud1 systemd[1]: Failed to reset devices.list on /system.slice/proc-swaps.mount: Operation not permitted
Apr 23 16:49:35 nextcloud1 systemd[1]: Failed to reset devices.list on /system.slice/rsyslog.service: Operation not permitted
Apr 23 16:49:35 nextcloud1 systemd[1]: Failed to reset devices.list on /system.slice/systemd-random-seed.service: Operation not permitted
Apr 23 16:49:35 nextcloud1 systemd[1]: Failed to reset devices.list on /system.slice/proc-sys-net.mount: Operation not permitted
Apr 23 16:49:35 nextcloud1 systemd[1]: Failed to reset devices.list on /system.slice/systemd-update-utmp.service: Operation not permitted
Apr 23 16:49:35 nextcloud1 systemd[1]: Failed to reset devices.list on /system.slice/sys-devices-virtual-net.mount: Operation not permitted
Apr 23 16:49:35 nextcloud1 systemd[1]: Failed to reset devices.list on /system.slice/proc-diskstats.mount: Operation not permitted
Apr 23 16:49:35 nextcloud1 systemd[1]: Failed to reset devices.list on /system.slice/proc-sysrq\x2dtrigger.mount: Operation not permitted
Apr 23 16:49:35 nextcloud1 systemd[1]: Failed to reset devices.list on /system.slice/dev-hugepages.mount: Operation not permitted
Apr 23 16:49:35 nextcloud1 systemd[1]: Failed to reset devices.list on /system.slice/proc-sys-fs-binfmt_misc.mount: Operation not permitted
Apr 23 16:49:35 nextcloud1 systemd[1]: Failed to reset devices.list on /system.slice/proc-uptime.mount: Operation not permitted
Apr 23 16:49:35 nextcloud1 systemd[1]: Failed to reset devices.list on /system.slice/systemd-journald.service: Operation not permitted
Apr 23 16:49:35 nextcloud1 systemd[1]: Failed to reset devices.list on /system.slice/sys-fs-fuse-connections.mount: Operation not permitted
Apr 23 16:49:35 nextcloud1 systemd[1]: Failed to reset devices.list on /system.slice/systemd-sysctl.service: Operation not permitted
Apr 23 16:49:35 nextcloud1 systemd[1]: Failed to reset devices.list on /system.slice/systemd-tmpfiles-setup.service: Operation not permitted
Apr 23 16:49:35 nextcloud1 systemd[1]: Failed to reset devices.list on /system.slice/apparmor.service: Operation not permitted
Apr 23 16:49:35 nextcloud1 systemd[1]: Failed to reset devices.list on /system.slice/dev-ptmx.mount: Operation not permitted
Apr 23 16:49:35 nextcloud1 systemd[1]: Failed to reset devices.list on /system.slice/dev-net-tun.mount: Operation not permitted
Apr 23 16:49:35 nextcloud1 systemd[1]: Failed to reset devices.list on /system.slice/systemd-remount-fs.service: Operation not permitted
Apr 23 16:49:35 nextcloud1 systemd[1]: Failed to reset devices.list on /system.slice/rc-local.service: Operation not permitted
Apr 23 16:49:35 nextcloud1 systemd[1]: Failed to reset devices.list on /system.slice/dev-lxd.mount: Operation not permitted
Apr 23 16:49:35 nextcloud1 systemd[1]: Failed to reset devices.list on /system.slice/systemd-journal-flush.service: Operation not permitted
Apr 23 16:49:35 nextcloud1 systemd[1]: Failed to reset devices.list on /system.slice/snapd.service: Operation not permitted
Apr 23 16:49:35 nextcloud1 systemd[1]: Failed to reset devices.list on /system.slice/dev-fuse.mount: Operation not permitted
Apr 23 16:49:35 nextcloud1 systemd[1]: Failed to reset devices.list on /system.slice/console-getty.service: Operation not permitted
Apr 23 16:49:35 nextcloud1 systemd[1]: Failed to reset devices.list on /system.slice/system-getty.slice: Operation not permitted
Apr 23 16:49:35 nextcloud1 systemd[1]: Failed to reset devices.list on /system.slice/ondemand.service: Operation not permitted
Apr 23 16:49:35 nextcloud1 systemd[1]: Failed to reset devices.list on /system.slice/proc-cpuinfo.mount: Operation not permitted
Apr 23 16:49:35 nextcloud1 systemd[1]: Failed to reset devices.list on /system.slice/sys-kernel-debug-tracing.mount: Operation not permitted
Apr 23 16:49:35 nextcloud1 systemd[1]: Failed to reset devices.list on /system.slice/dev-mqueue.mount: Operation not permitted
Apr 23 16:49:35 nextcloud1 systemd[1]: Failed to reset devices.list on /system.slice/cron.service: Operation not permitted
Apr 23 16:49:35 nextcloud1 systemd[1]: Failed to reset devices.list on /system.slice/systemd-user-sessions.service: Operation not permitted
Apr 23 16:49:35 nextcloud1 systemd[1]: Failed to reset devices.list on /system.slice/dev-.lxc-sys.mount: Operation not permitted
Apr 23 16:49:35 nextcloud1 systemd[1]: Failed to reset devices.list on /system.slice/networking.service: Operation not permitted
Apr 23 16:49:35 nextcloud1 systemd[1]: Failed to reset devices.list on /system.slice/-.mount: Operation not permitted
Apr 23 16:49:35 nextcloud1 systemd[1]: Failed to reset devices.list on /system.slice/dev-.lxc-proc.mount: Operation not permitted
Apr 23 16:49:35 nextcloud1 systemd[1]: Failed to reset devices.list on /system.slice/proc-meminfo.mount: Operation not permitted
Apr 23 16:49:35 nextcloud1 systemd[1]: Failed to reset devices.list on /system.slice/proc-stat.mount: Operation not permitted
Apr 23 16:49:35 nextcloud1 systemd[1]: Failed to reset devices.list on /system.slice/resolvconf.service: Operation not permitted
Apr 23 16:49:35 nextcloud1 systemd[1]: Mounted Ensure that the snap directory shares mount events..
-- Subject: Unit snap.mount has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit snap.mount has finished starting up.
--
-- The start-up result is done.
Apr 23 16:49:35 nextcloud1 systemd[1]: Failed to reset devices.list on /system.slice/snap-core-4407.mount: Operation not permitted
Apr 23 16:49:35 nextcloud1 systemd[1]: Mounting Mount unit for core...
-- Subject: Unit snap-core-4407.mount has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit snap-core-4407.mount has begun starting up.
Apr 23 16:49:35 nextcloud1 mount[329]: mount: wrong fs type, bad option, bad superblock on /var/lib/snapd/snaps/core_4407.snap,
Apr 23 16:49:35 nextcloud1 mount[329]: missing codepage or helper program, or other error
Apr 23 16:49:35 nextcloud1 mount[329]: In some cases useful info is found in syslog - try
Apr 23 16:49:35 nextcloud1 mount[329]: dmesg | tail or so.
Apr 23 16:49:35 nextcloud1 systemd[1]: snap-core-4407.mount: Mount process exited, code=exited status=32
Apr 23 16:49:35 nextcloud1 systemd[1]: Failed to mount Mount unit for core.
-- Subject: Unit snap-core-4407.mount has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit snap-core-4407.mount has failed.
--
-- The result is failed.
Apr 23 16:49:35 nextcloud1 systemd[1]: snap-core-4407.mount: Unit entered failed state.
Apr 23 16:49:35 nextcloud1 systemd[1]: Reloading.
Apr 23 16:49:35 nextcloud1 systemd[1]: Reloading.
Apr 23 16:49:40 nextcloud1 snapd[136]: 2018/04/23 16:49:40 Unsolicited response received on idle HTTP channel starting with "HTTP/1.0 408 Request Time-out\r\nCache-Control: no-cache\r\nConnection: close\r\nContent-Type: text/html\r\n\r\n<html><body><h1>408 Request Time-out</h1>\nYour browser didn't send a complete request in time.\n</body></html>\n";
Apr 23 16:49:42 nextcloud1 snapd[136]: 2018/04/23 16:49:42.533649 handlers.go:358: Reported install problem for "core" as 51a2af42-4716-11e8-89df-fa163ed44aae OOPSID
dmesg | tail
[ 78.732358] audit: type=1400 audit(1524502112.614:54): apparmor="STATUS" operation="profile_load" label="lxd-nextcloud1_</var/snap/lxd/common/lxd>//&:lxd-nextcloud1_<var-snap-lxd-common-lxd>:unconfined" name="/usr/lib/snapd/snap-confine//mount-namespace-capture-helper" pid=3226 comm="apparmor_parser"
[ 95.131824] Netfilter messages via NETLINK v0.30.
[ 95.149841] ip_set: protocol 6
[ 117.955186] audit: type=1400 audit(1524502151.842:55): apparmor="DENIED" operation="mount" info="failed flags match" error=-13 profile="lxd-ipa_</var/snap/lxd/common/lxd>" name="/" pid=4055 comm="(bash)" flags="rw, rslave"
[ 118.181402] audit: type=1400 audit(1524502152.068:56): apparmor="DENIED" operation="mount" info="failed flags match" error=-13 profile="lxd-ipa_</var/snap/lxd/common/lxd>" name="/" pid=4060 comm="(d-pkcs11)" flags="rw, rslave"
[ 121.500411] audit: type=1400 audit(1524502155.388:57): apparmor="DENIED" operation="mount" info="failed flags match" error=-13 profile="lxd-ipa_</var/snap/lxd/common/lxd>" name="/" pid=4172 comm="(kdcproxy)" flags="rw, rslave"
[ 122.724323] audit: type=1400 audit(1524502156.612:58): apparmor="DENIED" operation="mount" info="failed flags match" error=-13 profile="lxd-ipa_</var/snap/lxd/common/lxd>" name="/" pid=4190 comm="(httpd)" flags="rw, rslave"
[ 126.899731] audit: type=1400 audit(1524502160.788:59): apparmor="DENIED" operation="mount" info="failed flags match" error=-13 profile="lxd-ipa_</var/snap/lxd/common/lxd>" name="/" pid=4286 comm="(custodia)" flags="rw, rslave"
[ 130.499491] audit: type=1400 audit(1524502164.388:60): apparmor="DENIED" operation="mount" info="failed flags match" error=-13 profile="lxd-ipa_</var/snap/lxd/common/lxd>" name="/" pid=4362 comm="(ntpd)" flags="rw, rslave"
[ 152.791753] audit: type=1400 audit(1524502186.682:61): apparmor="DENIED" operation="mount" info="failed flags match" error=-13 profile="lxd-ipa_</var/snap/lxd/common/lxd>" name="/" pid=4834 comm="(keysyncd)" flags="rw, rslave"
rhetr
on 23 Apr 2018
i just ran lxc exec nextcloud -- apt install fuse -y and my problems appear to be solved for the most part: I ran into this error as well but running snap install nextcloud twice seems to have worked. I also had to run lxc config device add nextcloud modules disk source=/lib/modules path=/lib/modules for nextcloud to install completely.
rhetr
on 23 Apr 2018
👍2
❤1
Was this page helpful?
0 / 5 - 0 ratings
Related issues
rrva
·
5Comments
srkunze
·
3Comments
shaun-ba
·
3Comments
jsnjack
·
3Comments
spacekookie
·
3Comments
Most helpful comment
i just ran
lxc exec nextcloud -- apt install fuse -yand my problems appear to be solved for the most part: I ran into this error as well but runningsnap install nextcloudtwice seems to have worked. I also had to runlxc config device add nextcloud modules disk source=/lib/modules path=/lib/modulesfor nextcloud to install completely.