[Bug 2022927] Re: Busybox mount fails to mount Snaps
Christian Ehrhardt
2022927 at bugs.launchpad.net
Mon Jun 19 13:00:39 UTC 2023
Debian is at 1.36 already, but without your change landing upstream that
doesn't help us :-/ (This was released before on January 2023 anyway)
The upstream contribubution was nice, but stalled with http://lists.busybox.net/pipermail/busybox/2023-March/090211.html
It didn't come up again in April-June :-/
Was there any follow up to avoid this being Ubuntu delta forever?
Especially with something that changes behavior so that e.g. guides and howtos would behave differently between linux variants you'd usually want upstreams buy-in to avoid maintenance nightmare.
Would you mind following up with them and summarizing here about that progress to get it upstream?
P.S. by now you might want to set "mantic" in your debdiff changelog
stanza as that is what someone will eventually sponsor it to.
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to busybox in Ubuntu.
https://bugs.launchpad.net/bugs/2022927
Title:
Busybox mount fails to mount Snaps
Status in busybox package in Ubuntu:
New
Bug description:
Snapd tries to mount squashfs Snaps with non-standard mount flags like
"x-gdu.hide" and "x-gvfs-hide", both of which are used to indicate to
userspace programs that a given mount should not be shown in a list of
mounted partitions/filesystems. Busybox does not support these flags,
and so fails with "Invalid argument".
$ sudo busybox mount -t tmpfs -o x-gdu-hide test /tmp/test
mount: mounting test on /tmp/test failed: Invalid argument
These flags can likely be be safely ignored, as they don't actually
affect the functionality of the mount. This goes for all mount options
starting with "x-", as these generally denote non-standard mount
option "extensions".
I've created a patch against Busybox which adds an optional
configuration item to ignore all mount options beginning with "x-". An
additional verbose option has also been added to enable the ability to
report that the mount flags have been ignored, rather than silently
ignoring them.
This is a requirement for a customer project, where we are limited to
using Busybox (due to coreutils' GPL-3.0 licence) but would also
require using Snaps like checkbox for testing and verification. This
was posted on the Busybox mailing list a few months ago
(http://lists.busybox.net/pipermail/busybox/2023-March/090202.html)
but patch acceptance there seems to take quite a long time, and we
need this for the customer.
A PPA containing the patched Busybox version is available on the
project's Launchpad team: https://launchpad.net/~nemos-
team/+archive/ubuntu/ppa
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/2022927/+subscriptions
More information about the foundations-bugs
mailing list