network handling snap on core16 with base core18 fails to access /var/lib/dhcp
Bug #1862637 reported by
Ondrej Kubik
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| snapd |
Fix Released
|
Undecided
|
Zygmunt Krynicki | ||
Bug Description
snap: 2.43.2
core: 16-2.43.2
network handling snap with network-control interface
base: core18
in context of the snap /var/lib/dhcp directory is not mapped to host's /var/lib/dhcp
Additionally it's read only, so snap cannot use it, even though network-control interface allows so
This bug is not related to any particular project, it's been discovered while debugging networking snap.
Revision history for this message
| Zygmunt Krynicki (zyga) wrote | #1 |
| Changed in snapd: | |
| status: | New → Confirmed |
| summary: |
- network handling snap on core16 with base core18 fails to acmes + network handling snap on core16 with base core18 fails to access /var/lib/dhcp |
| description: | updated |
Revision history for this message
| Zygmunt Krynicki (zyga) wrote | #2 |
| Changed in snapd: | |
| status: | Confirmed → In Progress |
| assignee: | nobody → Zygmunt Krynicki (zyga) |
| milestone: | none → 2.44 |
Revision history for this message
| Zygmunt Krynicki (zyga) wrote | #3 |
| Changed in snapd: | |
| status: | In Progress → Fix Committed |
Revision history for this message
| Zygmunt Krynicki (zyga) wrote | #4 |
| Changed in snapd: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
For context, when snapd was first ported from 15.xx releases, that is when 16.04 first shipped, ubuntu-core devices crafted their own mount namespace and that same namespace was reused for snaps running in that environment. When snapd introduced support for bases and subsequently core18 snap was available on devices that otherwise booted with core (core16), this was changed so that snapd always crafts a pristine mount namespace that is not dependent on the initial mount namespace that snapd operates in.
Currently there are two supported execution modes, called legacy, which reuses real /, and is only used for ubuntu-core devices running with core at boot base and running a core-based snap, and normal, used in all classic devices and all core18 devices and core16 devices running snaps with another boot base.
We can add /var/lib/dhcp to the set of directories bridged over from the host. I will let mvo decide on release priority and design though.