Public bug reported:
Using snapd 2.0.9 on xenial on i386, snap commands hit a syscall error
on i386 unless "socketcall" is allowed in the profile, that should
perhaps be allowed by default as a workaround until the libseccomp issue
is resolved?
** Affects: snapd (Ubuntu)
Importance: High
Assignee: Jamie Strandboge (jdstrand)
Status: New
** Tags: snapd-interface
** Changed in: snapd (Ubuntu)
Importance: Undecided => High
** Summary changed:
- syscall error on i386
+ syscall error on i386 unless socketcall is allowed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1594675
Title:
syscall error on i386 unless socketcall is allowed
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1594675/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs