Closed v4nderstruck closed 6 days ago
Hi @v4nderstruck, that is not really a supported way of running Multipass, but if everything else seems to work, perhaps AppArmor is denying visibility of that directory to the Multipass daemon? Do you see anything in dmesg | grep apparmor=\"DENIED\"
? Does if work if there when the source path does not involve directories/files starting with dot?
BTW, others seemed to have had issues with the QEMU version from the AUR package: https://github.com/canonical/multipass/issues/3441#issuecomment-2007054913 . But I doubt that is related to your issue.
Hi, I have no apparmor running and regardless of whether the path has a "." or not, it does not work.
apparmor module is loaded.
apparmor filesystem is not mounted.
any other ideas?
Hi @v4nderstruck, what compiler/version did you use to build? I ask because our CMake may be allowing compilers without full standard C++17 support yet (requiring only -std=C++1z). If that is your case, it is possible that you didn't have full compliant std::filesystem
library support yet. We have had cases of compilers with incomplete C++17 support causing runtime issues in the past.
Hi @v4nderstruck!
Could you please provide the answers to the question @ricab asked? If we don't hear back from you soon, we will close this issue. Thanks!
Closing for lack of activity.
Describe the bug Hi, I'm trying to mount a directory and multipass fails with "Mount source path ... does not exist." I have built multipass from source (running on Manjarom, used the AUR package https://aur.archlinux.org/packages/canonical-multipass ) and other functionalities seem to work fine (creating VMs, shell...)
To Reproduce for example, I try mounting my neovim config dir
multipass mount /home/v4nderstruck/.config/nvim dev:/home/ubuntu/.config/nvim
Expected behavior Mounting should work
Logs Nothing really usefull in daemon logs. I set it to trace and there is no report (except certificate validation) when mounting...
Mouting with Command with
-vvvv
And I have part of the strace where things may be interesting. Should not be a permission issue and the directory seems to exist.
Additional info
local driver qemu
Additional context Add any other context about the problem here.