FILESYSTEM IN USERSPACE (FUSE) development
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Skye Soss <skye@soss.website>
Cc: fuse-devel <fuse-devel@lists.linux.dev>
Subject: Re: fuservicemount as a systemd storage provider
Date: Tue, 22 Sep 2026 14:56:04 -0700	[thread overview]
Message-ID: <20260922215604.GX6283@frogsfrogsfrogs> (raw)
In-Reply-To: <1a0c03229ed.1b908e3c391748.1531711527420340195@soss.website>

On Sun, Sep 20, 2026 at 02:01:48PM -0500, Skye Soss wrote:
> The fuservicemount infrastructure that's currently being developed in the libfuse repository allows an administrator to
> setup a service that can create sandboxed filesystem implementations on-demand.
> 
> There is a very similar interface that's being developed in systemd (added in 261) called Storage Providers[1].
> The directory /run/systemd/io.systemd.StorageProvider/ contains Unix domain sockets, each of which is backed by a Varlink
> service. The interface (modulo metadata + options) is essentially:
> 
> Acquire(name: string) -> (fileDescriptor: int)
> 
> systemd also provides a mount helper so that `mount -t storage` can transparently use the storage provider interface.
> 
> This seems like a very similar kind of setup to fuservicemount + mount.fuse, and I'm curious if there's anything missing
> from the systemd interface that would stop fuservicemount from being implement in those terms.

Can't work on any environment that lacks systemd (Devuan, BSDs, etc)

--D

> I believe that systemd-nspawn and systemd-vmspawn are going to be extended to create mounts from these interfaces, so
> compatibility would be useful.
> 
> [1]: https://www.freedesktop.org/software/systemd/man/latest/systemd-storage-fs@.service.html
> 

      reply	other threads:[~2026-09-22 21:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-20 19:01 fuservicemount as a systemd storage provider Skye Soss
2026-09-22 21:56 ` Darrick J. Wong [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20260922215604.GX6283@frogsfrogsfrogs \
    --to=djwong@kernel.org \
    --cc=fuse-devel@lists.linux.dev \
    --cc=skye@soss.website \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox