lxd-profile doesn't contain lxc.cgroup.devices.allow
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Kubernetes Control Plane Charm |
Fix Released
|
High
|
Tim Van Steenburgh | ||
Kubernetes Worker Charm |
Fix Released
|
High
|
Tim Van Steenburgh |
Bug Description
When deploying charmed-kubernetes on LXD I'm seeing containers fail with this error:
message: 'failed to create containerd task: OCI runtime create failed: container_
starting container process caused "process_
caused \"process_
caused \\\"failed to write \\\\\\\"a *:* rwm\\\\\\\" to \\\\\\\
write /sys/fs/
operation not permitted\\\"\"": unknown'
Adding the following to my lxd profile solves the issue.
lxc.cgroup.
However, keys are not merged and the charm installs it's own profile after any model-specific profiles are applied over writing the change. This means you have to define a profile with
raw.lxc: |
lxc.
lxc.
lxc.
lxc.cap.drop=
Then apply the profile after the charm has installed, and restart for it to work. Including the cgroup lxc raw value in the lxd-profile would make the manual steps unnecessary and lxd installs would just work out of the box.
no longer affects: | charm-aws-iam |
Changed in charm-kubernetes-master: | |
importance: | Undecided → Critical |
Changed in charm-kubernetes-worker: | |
importance: | Undecided → Critical |
Changed in charm-kubernetes-master: | |
status: | Confirmed → Triaged |
Changed in charm-kubernetes-worker: | |
status: | Confirmed → Triaged |
Changed in charm-kubernetes-master: | |
assignee: | nobody → Tim Van Steenburgh (tvansteenburgh) |
Changed in charm-kubernetes-worker: | |
assignee: | nobody → Tim Van Steenburgh (tvansteenburgh) |
Changed in charm-kubernetes-master: | |
milestone: | none → 1.18+ck1 |
Changed in charm-kubernetes-worker: | |
milestone: | none → 1.18+ck1 |
tags: | added: sts |
tags: | removed: review-needed |
Changed in charm-kubernetes-master: | |
status: | In Progress → Fix Committed |
Changed in charm-kubernetes-worker: | |
status: | In Progress → Fix Committed |
Changed in charm-kubernetes-master: | |
importance: | Critical → High |
Changed in charm-kubernetes-worker: | |
importance: | Critical → High |
Changed in charm-kubernetes-master: | |
status: | Fix Committed → Fix Released |
Changed in charm-kubernetes-worker: | |
status: | Fix Committed → Fix Released |
If you can share what version of Ubuntu this occurred on and what version of LXD you were running, it would help us reproduce it.