Open AlanGriffiths opened 4 years ago
Hmm I was unable to reproduce…
adm
groupmultipass shell
worked just fine…Maybe it was a temporary problem? Can you reproduce still?
Same system (installed from the rawhide daily a couple of weeks ago, and updated since):
[alan@localhost egmde-snap]$ snapcraft
WARNING: cgroup v2 is not fully supported yet, proceeding with partial confinement
Launching a VM.
WARNING: cgroup v2 is not fully supported yet, proceeding with partial confinement
start failed: The following errors occurred:
snapcraft-egmde: timed out waiting for response
WARNING: cgroup v2 is not fully supported yet, proceeding with partial confinement
An error occurred with the instance when trying to start with 'multipass': returned exit code 2.
Ensure that 'multipass' is setup correctly and try again.
[alan@localhost egmde-snap]$ multipass list
WARNING: cgroup v2 is not fully supported yet, proceeding with partial confinement
Name State IPv4 Image
snapcraft-egmde Delayed Shutdown UNKNOWN Ubuntu Snapcraft builder for Core 18
OK reproduced. The instance isn't getting an IP for some reason.
LXD has the same problem: lxc/lxd#7150, it's firewalld
blocking the DHCP requests.
Disabling firewalld
is a workaround: sudo systemctl stop firewalld
.
The workaround:
firewall-cmd --zone=trusted --change-interface=mpqemubr0 --permanent
firewall-cmd --zone=trusted --change-interface=mpqemubr0 --permanent
Until multipass gets confined, that could be added to the install hook:
if [ "$(sed -Ene 's/^ID=(.*)/\1/p' /etc/os-release)" == "fedora" ]
then
firewall-cmd --zone=trusted --change-interface=mpqemubr0 --permanent
fi
:wink:
I think we'll have to document that instead.
Doesn't work for me
I think we'll have to document that instead.
LXD is also broken on Fedora 32.
✗ lxc launch ubuntu:18.04 xxx
WARNING: cgroup v2 is not fully supported yet, proceeding with partial confinement
Creating xxx
Starting xxx
✗ lxc exec xxx -- bash
WARNING: cgroup v2 is not fully supported yet, proceeding with partial confinement
root@xxx:~# ping google.com
ping: google.com: Temporary failure in name resolution
root@xxx:~#
Why podman
and docker
containers don't have such problems on Fedora?
I had the same issue trying out snapcraft on Fedora 33 for the first time. I did two things, not sure if the first is necessary:
Now
> multipass list WARNING: cgroup v2 is not fully supported yet, proceeding with partial confinement Name State IPv4 Image snapcraft-my-first-snap Delayed Shutdown 10.137.247.131 Ubuntu Snapcraft builder for Core 18
So at least I have an IP, but still the connection inside the VM does not work. - If I find out more, will let you know.
I'm having this issue on Debian using UFW. Any suggestion what the equivalent rule would be for UFW to work without having to disable it?
OK I answered my own question, in case any other UFW users are having this issue, the following rule worked for me:
sudo ufw allow in on mpqemubr0 to any
@JmaJeremy I also came across the same problem as you and ended with having my snaps built remotely (snapcraft remote-build
). It's not a solution, not even a work around and to make it worse, it's even super slow but it works!
So at least I have an IP, but still the connection inside the VM does not work. - If I find out more, will let you know.
Yes. Even disabling firewalld didn't help.
I've run into this again. What is needed to make multipass
work correctly on Fedora out of the box?
Hey @abitrolly,
I commented at https://github.com/canonical/multipass/issues/2564#issuecomment-1125994537 about the challenges of automatically making Multipass work with firewalld
.
Thanks!
Describe the bug Trying to package a snap using snapcraft on Fedora rawhide. Initially this failed with a permission error on
/var/snap/multipass/common/multipass_socket
After adding myself to
adm
I then get:Logs