@zolika84 please start a new bug with details of what you expect/fail to
see from snapd on those systems, we don't explicitly support WSL2 yet,
there are some forum topics around that explain how you can make it
work, but snapd doesn't work OOTB in WSL2. I'm not sure what the issue
is with running
Issue is still the same - the issue comes out when you try to run snapd
on a chromebook (linux terminal), or in WSL2.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1628289
Title:
snapd should
Indeed snapd carries this on its own.
** Changed in: snappy
Status: Incomplete => Fix Released
** Changed in: snapd (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
As for host restrictions I need to use LXC too (not lxd), what I needed
to get this working was just:
lxc config as:
# Mount local kernel modules dir, snap needs it for its bind-mount
lxc.mount.entry = /lib/modules lib/modules none bind,create=dir,optional 0 0
# Mounting fuse (for snap
My understand of the status is that snapd grew its own code for mounting
snaps via fuse, which would make this MIR unnecessary.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1628289
Title:
snapd
This MIR has been completed, but squashfuse is still not in main (and
apparently not Depend-ed on by snapd).
None of the referenced bugs mentions squashfuse, what is the status of
this?
** Changed in: snapd (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: snappy
Status: In
Bug 1756173 is set to put 2.32 into bionic and SRU to trusty, xenial,
and artful.
So if you're interested in this fix, watch that bug.
** Description changed:
We're finally making progress on the apparmor stacking and snapd in
container front. The next LXD release will include the needed
** Also affects: snapd (Ubuntu)
Importance: Undecided
Status: New
** Changed in: snapd (Ubuntu)
Status: New => Confirmed
** Changed in: snapd (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I removed the "snap" package bug task, as I doubt this bug affects the
gene finder.
** No longer affects: snap (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1628289
Title:
snapd should
** Also affects: snap (Ubuntu)
Importance: Undecided
Status: New
** Changed in: snap (Ubuntu)
Status: New => Confirmed
** Changed in: snap (Ubuntu)
Importance: Undecided => Medium
** Changed in: snap (Ubuntu)
Status: Confirmed => Fix Committed
** Changed in: snap
This is fixed in snapd under https://github.com/snapcore/snapd/pull/4049
It will be fixed in snapd 2.31.2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1628289
Title:
snapd should depend on
Following previous discussions and proposals I understand there are some
issues with getting 'squashfuse' installed automatically for container
workloads.
In the meantime, for improved UX, would having "snap install" command
inform operator of 'squashfuse' dependency for in-container operation be
On Sat, Nov 18, 2017 at 11:25:49PM +0300, Marat Khalili wrote:
> > The problem in your case is that you're trying to get this to work with LXC
> > rather than LXD.
>
> Should I understand it as snapd is not currently supported under LXC? No way
> to reproduce manually in LXC whatever LXD does?
> The problem in your case is that you're trying to get this to work
with LXC rather than LXD.
Should I understand it as snapd is not currently supported under LXC? No
way to reproduce manually in LXC whatever LXD does?
> I'd very strongly recommend against anyone using the configuration
above
The problem in your case is that you're trying to get this to work with
LXC rather than LXD.
LXD images ship with a /lib/modules directory, ship with fuse pre-
installed, LXD sets up /dev/fuse by default for you and comes with
apparmor namespacing support so the container can load apparmor
My problem was solved by:
1. Adding the following lines to the container config, then stopping and
starting the container:
---
# Make snapd work
lxc.aa_profile = unconfined
# don't drop: mac_admin mac_override
lxc.cap.drop =
lxc.cap.drop = sys_time sys_module sys_rawio
lxc.hook.autodev = sh
---
root@test:/# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.3 LTS
Release:16.04
Codename: xenial
root@test:/# apt install squashfuse
Reading package lists... Done
Building dependency tree
Reading state information... Done
Responding to comments #36 and #37, I can confirm that a xenial
container (x1) in a xenial host can install snaps after you install
squashfuse.
Without squashfuse:
root@x1:~# snap install hello-world
error: cannot perform the following tasks:
- Mount snap "core" (3247) ([start
It seems 16.10 and 17.04 are still affected by this problem. Don't know
about 17.10 as I haven't been able to make it work properly under
LXC/LXD with Juju.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
> Just to update my previous comment: poking around Stéphane Graber's
blog a bit suggests to me that I really shouldn't expect success with
this using less than 16.10.
Can someone please confirm it is really true? Bug description contains
Xenial, and this discussion --
Just to update my previous comment: poking around Stéphane Graber's blog
a bit suggests to me that I really shouldn't expect success with this
using less than 16.10.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I've installed squashfuse on my Ubuntu LXC container (under Ubuntu
16.04.2) and then tried to install the NextCloud snap, but it's still
failing with this same error:
error: cannot perform the following tasks:
- Mount snap "core" (2381) ([start snap-core-2381.mount] failed with exit
status 1:
Hi,
I am facing the same issue with Ubuntu 16.04.2 LTS.
I get the below error;
@master:~$ sudo snap install conjure-up --classic
error: cannot perform the following tasks:
- Download snap "core" (2381) from channel "stable" (Get
squashfuse must be installed in the container that's going to run snapd
not on the host, so it can't be a dependency of LXD itself.
The image that's used for the LXD containers is an unmodified Ubuntu
cloud image. If we do go with seeding squashfuse for this, it would mean
that it would be
I understand this is high priority, but the PR you just wrote is a poor
copy of the older one from February where we attempted the same thing,
and it's just as wrong for the same reasons.
Is there really no other way to pull squashfuse onto the lxd images? I
don't know how they're built, but
Here's a pull request:
https://github.com/snapcore/snapd/pull/3605
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1628289
Title:
snapd should depend on squashfuse (for use in containers)
To manage
This is high priority.
** Changed in: squashfuse (Ubuntu)
Importance: Undecided => High
** Changed in: squashfuse (Ubuntu Xenial)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: squashfuse (Ubuntu)
Assignee: Matthias Klose (doko) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1628289
Title:
snapd should depend on squashfuse (for use in
You meant https://github.com/snapcore/snapd/pull/2856
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1628289
Title:
snapd should depend on squashfuse (for use in containers)
To manage notifications
https://github.com/snapcore/snapd/pull/2830
** Changed in: snappy
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/1628289
Title:
snapd should depend on
doko tells me that we now need snapd to depend on squashfuse so we can
finish the promotion to main.
mvo: Can you please do that?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1628289
Title:
snapd
Autopkgtest added and passed in zesty.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1628289
Title:
snapd should depend on squashfuse (for use in containers)
To manage notifications about this bug
Should be easy enough to have an autopkgtest create a minimal squashfs
filesystem and mount it, I'll upload something along those lines to
Zesty. I'm assuming you don't need me to also SRU said autopkgtest to
all the stable releases until we have something more user relevant to
SRU right?
--
You
MIR review:
- this looks fine, but the package doesn't come with a testsuite.
- would it be possible to add a simple autopkg test?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1628289
Title:
Yeah, a recommend would be absolutely fine here and wouldn't cause "apt
upgrade" to hold snapd, if I recall correctly, that's in fact what I
first requested.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
We have to be careful with new dependencies because those cause issues
for 'apt-get update'.
Mark
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1628289
Title:
snapd should depend on squashfuse
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: squashfuse (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1628289
Title:
As requested by mvo above, this bug is now the MIR for squashfuse. The
same package is in zesty, yakkety and xenial so the result of the review
should apply equally to all series.
## Paperwork
Availability: in universe in all relevant series
Rationale: required for snapd inside LXD containers
There is no point in SRUing to trusty so we won't be doing that. The
reason is that trusty containers will never be able to run snapd inside
them due to a decision not to enable apparmor nesting inside trusty
containers.
Trusty users are expected to run xenial containers if they care about
Resetting bug status for MIR portion. I generally find it easier to
follow MIR bugs when they are separate, but it's fine, we can do it here
too.
Doko, can you take this one?
** Changed in: squashfuse (Ubuntu)
Status: Fix Released => New
** Changed in: squashfuse (Ubuntu)
Assignee:
I looked into this today and to move forward we need:
- a MIR for squashfuse as snapd is in main
- an upload of squashfuse to trusty because we support that as well now
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: snappy
Status: Fix Released => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1628289
Title:
snapd should depend on squashfuse (for use in containers)
To manage
Why was this marked as Fix released? As far as I can tell, snapd still
doesn't depend on squashfuse...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1628289
Title:
snapd should depend on squashfuse
** Changed in: snappy
Status: New => Fix Committed
** Changed in: snappy
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/1628289
Title:
snapd
Confirmed that squashfuse works as expected on Xenial.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1628289
Title:
snapd
Marking the squashfuse side of this bug as fix released.
Now that squashfuse is available in xenial, yakkety and zesty, can
someone please change snapd to depend on it so that users of snaps
inside containers don't need to manually install it?
--
You received this bug notification because you
This bug was fixed in the package squashfuse -
0.1.100-0ubuntu1~ubuntu16.04.1
---
squashfuse (0.1.100-0ubuntu1~ubuntu16.04.1) xenial; urgency=medium
* No-change backport to xenial (LP: #1628289)
-- Stéphane Graber Thu, 29 Sep 2016 12:08:47
-0400
** Changed
Hello Stéphane, or anyone else affected,
Accepted squashfuse into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/squashfuse/0.1.100-0ubuntu1~ubuntu16.04.1
in a few hours, and then in the -proposed repository.
Please help us by testing this
@mark, oh, sorry, i should have mentioned that i was talking about
images here :) not classic. for classic there need to be feature
backports indeed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Superstars, thank you :)
Mark
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1628289
Title:
snapd should depend on squashfuse (for use in containers)
To manage notifications about this bug go to:
The two kernel features we need for snaps in LXD are both scheduled for
backporting to the 4.4 kernel once we're satisfied that they are stable
in Yakkety's 4.8.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
We can't ask people to install a new kernel to get one part of LXD. That
might work for 17.10, but not this soon after 16.04.
Mark
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1628289
Title:
kernel wise i was actually wondering if we shouldnt perhaps focus on the
-hwe lts kernels (probably a valuable topic for the sprint), but i guess
the 4.8 release from yakkety might be to late for us for GA to get
enough testing.
--
You received this bug notification because you are a member of
Uploaded to the xenial queue.
** Changed in: squashfuse (Ubuntu)
Status: New => In Progress
** Changed in: squashfuse (Ubuntu)
Assignee: (unassigned) => Stéphane Graber (stgraber)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Also affects: squashfuse (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1628289
Title:
snapd should depend on squashfuse (for use in
55 matches
Mail list logo