Re: Inquiry regarding FUSE filesystem behavior with mount bind in docker

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, Jan 10, 2025 at 9:56 PM Miklos Szeredi <miklos@xxxxxxxxxx> wrote:
>
> On Fri, 10 Jan 2025 at 10:32, Julian Sun <sunjunchao2870@xxxxxxxxx> wrote:
> >
> > Dear Respected Maintainers,
> >
> > I hope this email finds you well.
> >
> > Recently, one of our customers encountered the following issue:
> > A directory from a FUSE filesystem(a local union fs) on the host
> > machine was shared inside a Docker container using mount bind. After
> > updating the FUSE filesystem (by killing the existing FUSE process,
> > replacing the binary, and starting a new FUSE process), any operation
> > on the shared directory inside the Docker container failed with the
> > error 'Transport endpoint is not connected'.
>
> Restarting a fuse server is possible by storing the "/dev/fuse" fd and
> passing it to the new instance.  This obviously needs support from the
> server.  See some related discussions here:
>
>   https://lore.kernel.org/all/20240524064030.4944-1-jefflexu@xxxxxxxxxxxxxxxxx/

Thanks! It's exactly what I wanted, very helpful.
>
> I'm not interested in a solution that bypasses the server completely.
>
> Thanks,
> Miklos


Thanks,
-- 
Julian Sun <sunjunchao2870@xxxxxxxxx>





[Index of Archives]     [Linux Ext4 Filesystem]     [Union Filesystem]     [Filesystem Testing]     [Ceph Users]     [Ecryptfs]     [NTFS 3]     [AutoFS]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Cachefs]     [Reiser Filesystem]     [Linux RAID]     [NTFS 3]     [Samba]     [Device Mapper]     [CEPH Development]

  Powered by Linux