3.1 doesn't work with Travis

Bug #1815319 reported by anatoly techtonik
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Snapcraft
New
Undecided
Unassigned

Bug Description

Running snapcraft with sudo gives:

$ sudo snapcraft
Launching a VM.
launch failed: CPU does not support KVM extensions.
An error occurred when trying to launch the instance with 'multipass': returned exit code 2.
Ensure that 'multipass' is setup correctly and try again.
The command "sudo snapcraft" exited with 2.

https://travis-ci.org/sdg-mit/gitless/jobs/491046025#L205

Running without sudo:

$ snapcraft
Launching a VM.
launch failed: multipass socket access denied
Please check that you have read/write permissions to '/run/multipass_socket'
An error occurred when trying to launch the instance with 'multipass': returned exit code 2.
Ensure that 'multipass' is setup correctly and try again.
The command "snapcraft" exited with 2.

https://travis-ci.org/sdg-mit/gitless/jobs/491034488#L203

Revision history for this message
Kemel Zaidan aka Legendario (kemelzaidan) wrote :

I have exactly the first error but while trying to run snapcraft without sudo. I'm trying to build a C++ software snap in a 16.04 virtualbox VM since I'm running 18.10 on my laptop.

Revision history for this message
Kemel Zaidan aka Legendario (kemelzaidan) wrote :

I understood that it's happening because I'm running snapcraft inside a vm and the virtual hardware in the guest system does not support Intel VT. So there should be a way to build the snap without using multipass.

Are you using a VM too @anatoly techtonik?

Revision history for this message
Peter (peter-frohberg) wrote :

I wanted to play with snapcraft in a virtualbox machine, so my system stays clean, and I get the same error as well. Is there at least a workaround?

Revision history for this message
Sergio Schvezov (sergiusens) wrote :

You can use --destructive-mode considering you are running snapcraft from a sane environment.
Alternatively, --use-lxd is coming as an option through LP: #1805221

Revision history for this message
Sergio Schvezov (sergiusens) wrote :

Considering the latter linked bug and the former comment on how to get around the VM creation I am proceeding to mark this bug as a dup

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.