Skip to content

Conversation

@gabrielmougard
Copy link
Contributor

@gabrielmougard gabrielmougard commented Jan 13, 2025

closes #13406

If the path is not absolute, the mount will be created at /run/lxd_agent/<path>, since the mount command executed below originates from the lxd-agent binary that is in the /run/lxd_agent directory. This is not ideal and not consistent with the way mounts are handled with containers. We then make the path absolute.

The clean unmounting process will be handled in #12700

If the path is not absolute, the mount will be created at `/run/lxd_agent/<path>`,
since the mount command executed below originates from the `lxd-agent` binary that is in the `/run/lxd_agent` directory.
This is not ideal and not consistent with the way mounts are handled with containers. We then make the path absolute.

Signed-off-by: Gabriel Mougard <[email protected]>
@tomponline
Copy link
Member

ta

@tomponline tomponline merged commit 71fae76 into canonical:main Jan 14, 2025
27 of 28 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Hot plugging filesystem volume into VM with relative path causes it to be mounted under /run/lxd_agent/

2 participants