This bug was fixed while snap-confine was a separate package. I'm
marking the snappy task as fix-released.
** Changed in: snappy
Status: In Progress => Fix Released
** Project changed: snappy => snapd
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Yakkety still has 1.0.43.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1630789
Title:
normal users can't run snaps inside of LXD containers
To manage notifications about this bug go to:
https://bu
Nowadays xenial-updates has an ever higher version of snap-confine: 2.21
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1630789
Title:
normal users can't run snaps inside of LXD containers
To manage
** Changed in: snap-confine (Ubuntu Xenial)
Importance: Undecided => High
** Changed in: snap-confine (Ubuntu Yakkety)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
Hello Tyler, or anyone else affected,
Accepted snap-confine into yakkety-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/snap-
confine/1.0.44-0ubuntu1~16.10 in a few hours, and then in the -proposed
repository.
Please help us by testing this new packa
** Description changed:
+ [Impact]
+
+ TBD
+
+ [Test Case]
+
+ Look below for a test case.
+
+ [Regression Potential]
+
+ TBD
+
+ [Other Info]
+
+ * snap-confine is technically an integral part of snapd which has an SRU
+ exception and is allowed to introduce new features and take advantage
** Changed in: snap-confine
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1630789
Title:
normal users can't run snaps inside of LXD containers
To manage
** Changed in: snap-confine
Milestone: None => 1.0.44
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1630789
Title:
normal users can't run snaps inside of LXD containers
To manage notifications
This bug was fixed in the package snap-confine - 1.0.43-0ubuntu1~16.04.1
---
snap-confine (1.0.43-0ubuntu1~16.04.1) xenial-proposed; urgency=medium
* Backport from 16.10 (LP: #1630040)
snap-confine (1.0.43-0ubuntu1) yakkety; urgency=medium
* New upstream release (LP: #1630479, L
This can't really be tested yet for snap-confine in xenial proposed
because the required packages are not yet in xenial. I tried bringing
packages from yakkety and yakkety-proposed, but that didn't work, it was
just a long shot. It even seems there is still a PR in flight for snapd.
I checked the
This bug was fixed in the package snapd - 2.16+16.10ubuntu1
---
snapd (2.16+16.10ubuntu1) yakkety; urgency=medium
* systemd/systemd.go, systemd/systemd_test.go: Correct the mount arguments
when mounting with squashfuse (LP: #1630789)
-- Tyler Hicks Thu, 06 Oct 2016 18:49:40
** Changed in: snapd (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1630789
Title:
normal users can't run snaps inside of LXD containers
To manag
** Changed in: snapd (Ubuntu)
Assignee: (unassigned) => Tyler Hicks (tyhicks)
** Changed in: snapd (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/163
Pull request for snapd: https://github.com/snapcore/snapd/pull/2112
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1630789
Title:
normal users can't run snaps inside of LXD containers
To manage noti
This bug was fixed in the package snap-confine - 1.0.43-0ubuntu1
---
snap-confine (1.0.43-0ubuntu1) yakkety; urgency=medium
* New upstream release (LP: #1630479, LP: #1630492, LP: #1628612)
* debian/patches/lp1630789.patch: allow running snaps by non-root users in
LXD containe
** Changed in: snappy
Status: Triaged => In Progress
** Changed in: snappy
Assignee: (unassigned) => Tyler Hicks (tyhicks)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1630789
Title:
n
Hello Tyler, or anyone else affected,
Accepted snap-confine into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/snap-
confine/1.0.43-0ubuntu1~16.04.1 in a few hours, and then in the
-proposed repository.
Please help us by testing this new pack
1.0.43-0ubuntu1 uploaded to yakkety.
** Changed in: snap-confine (Ubuntu)
Status: In Progress => Fix Committed
** Also affects: snap-confine
Importance: Undecided
Status: New
** Changed in: snap-confine
Importance: Undecided => High
** Changed in: snap-confine
Status:
** Changed in: snap-confine (Ubuntu)
Status: Triaged => In Progress
** Changed in: snap-confine (Ubuntu)
Assignee: (unassigned) => Jamie Strandboge (jdstrand)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
I made an unfortunate typo in the following sentence found in comment
#4:
This explains the AppArmor denial from comment #3 containing
"fsuid=296608 ouid=0". The setuid-container-root snap-confine task is
correctly running as fsuid 296608 (container_ns root) but the mountinfo
inode is correctly as
Problem #3, the final problem, is due to a missing AppArmor rule needed
when the following PR was merged:
https://github.com/snapcore/snap-confine/pull/145
After fixing the squashfuse mounts, as mentioned in comment #3, and
dropping the "owner" conditional, as mentioned in comment #4 (be sure t
21 matches
Mail list logo
