lxd-agent-loader tmpfs too small for some LXD hosts

Bug #2058302 reported by Simon Déziel
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
lxd-agent-loader (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

When the host uses a manually compiled LXD where binaries were not stripped, the `lxd-agent` can be ~31MiB big. This binary is copied inside the VM guest when the VM boots up. This copy operation can fail as the tmpfs in the VM is mounted with `size=25MiB`.

This binary is then tentatively copied into any virtual machine instance where that copy can fail because the tmpfs' size is set to 25MiB:

$ lxc launch ubuntu-minimal-daily:24.04 v1 --vm
Creating v1
Starting v1
$ lxc exec v1 -- mount | grep /run/lxd_agent
tmpfs on /run/lxd_agent type tmpfs (rw,nosuid,nodev,noatime,size=25600k,mode=700,inode64)

Related branches

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package lxd-agent-loader - 0.7

---------------
lxd-agent-loader (0.7) noble; urgency=medium

  * d/lxd-agent-setup.postinst: Cleanup former unit files (LP: #2054814)
  * lxd-agent-setup: Bump /run/lxd_agent size to 50M (LP: #2058302)
  * lxd-agent-setup: Attempt to restore SELinux labels (LP: #2058303)

 -- Simon Deziel <email address hidden> Tue, 13 Feb 2024 16:48:15 -0500

Changed in lxd-agent-loader (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.