"mojo project-new --container lxd" fails when ACLs aren't enabled
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mojo: Continuous Delivery for Juju |
Triaged
|
Medium
|
Unassigned |
Bug Description
"mojo project-new --container lxd" eventually calls setfacl to let the user in the container write to the bind-mounted project dir. But this fails with "Operation not supported" by default, since ACLs generally have to be explicitly enabled per filesystem.
When running services in LXD for development we generally use a UID mapping trick to have the container user use the parent user's UID. One way to do that is documented on https:/
When running mojo itself inside a nesting-capable LXD container on ZFS, something like "sudo zfs set acltype=posixacl ssd/containers/
Changed in mojo: | |
status: | New → Confirmed |
status: | Confirmed → Triaged |
importance: | Undecided → Medium |