need writable-path for snappy
Bug #1632272 reported by
You-Sheng Yang
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical System Image |
Fix Released
|
Critical
|
You-Sheng Yang | ||
lxc-android-config (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Snappy writes to /etc/systemd/
Related branches
lp:~vicamo/lxc-android-config/writable-path-for-snapd
- Łukasz Zemczak: Approve (community)
- You-Sheng Yang (community): Needs Fixing
- Thomas Voß: Pending requested
-
Diff: 10 lines (+3/-0)1 file modifiedetc/system-image/writable-paths (+3/-0)
Changed in canonical-devices-system-image: | |
milestone: | none → x1 |
tags: | added: snappy |
Changed in canonical-devices-system-image: | |
importance: | Undecided → Critical |
status: | New → Confirmed |
Changed in canonical-devices-system-image: | |
status: | Confirmed → Fix Released |
assignee: | nobody → Vicamo Yang (vicamo) |
To post a comment you must log in.
About /etc/systemd/ system, here is an example:
# snap install hello-world system/ snap-ubuntu\ x2dcore- 425.mount. mD10qv5dWM0c: read-only file system)
error: cannot perform the following tasks:
- Mount snap "ubuntu-core" (425) (open /etc/systemd/
However, we should generally keep rootfs as read-only, and currently we haven't reach the step to allow user installing snap packages at will. So I'm to propose a mp to include /snap and /var/lib/snapd only.