/usr/lib/snapd unmounted in app + core18 + core (tooling) use case; possibly on core18 refresh
Bug #1821302 reported by
Alberto Donato
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| snapd |
Triaged
|
High
|
Zygmunt Krynicki | ||
Bug Description
While developing on the maas snap I use "snap try" inside a (bionic) LXD container.
I often run rsync to copy updated files (see https:/
On some occasions, the snaps stops working. Both CLI commands and the daemon report "execv failed: No such file or directory" errors.
After some digging (thanks to Zyga) turns out that /usr/lib/snapd inside the snap is not mounted (so no snap-exec is found).
The "core18" snap (which maas uses as base) has recently refreshed (I was tracking edge), although I can't be sure that the issue started right after the refresh).
Attached are /proc/self/
Revision history for this message
| Alberto Donato (ack) wrote | #1 |
Revision history for this message
| Alberto Donato (ack) wrote | #2 |
Revision history for this message
| Alberto Donato (ack) wrote | #3 |
Revision history for this message
| Alberto Donato (ack) wrote | #4 |
| Changed in snapd: | |
| status: | New → Triaged |
| assignee: | nobody → Zygmunt Krynicki (zyga) |
| importance: | Undecided → High |
| Changed in snapd: | |
| milestone: | none → 2.39 |
| importance: | High → Critical |
| Changed in snapd: | |
| importance: | Critical → High |
To post a comment you must log in.
Here's the strace output when trying to run the CLI
$ sudo snap run --strace=--raw maas
execve(
fstat(2, {st_mode=
write(2, "/usr/bin/strace: exec: Permissio"..., 41/usr/bin/strace: exec: Permission denied
) = 41
getpid() = 21884
exit_group(1) = ?
+++ exited with 1 +++
error: exit status 1