New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 841787 link

Starred by 108 users

Issue metadata

Status: Verified
Owner:
Closed: Jan 11
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Feature


Show other hotlists

Hotlists containing this issue:
LXD


Sign in to add a comment

support fuse in termina images

Project Member Reported by vapier@chromium.org, May 10 2018

Issue description

should investigate enabling fuse in our termina images.  i thought it had already been looked at (at least lightly), but can't find details in a quick search.
 
Labels: Hotlist-Crostini-Platform

Comment 2 by pkern@google.com, May 17 2018

Cc: pkern@google.com
Taking into account the limitation of the containers for loading custom kernel modules, having the working fuse will be very valuable. 
Enabling fuse in the kernel would allow snapd to work in containers via squashfuse.  Would be a great small addition.
Taking into account the limitation of the containers for loading custom kernel modules, having the working fuse will be very valuable. 

One can mount Google Drive inside the container for instance. 
> Taking into account the limitation of the containers for loading custom kernel modules, having the working fuse will be very valuable.

You can simply tell LXD to load the kernel module by setting

linux.kernel_modules

either in the default profile to apply to all containers or to specific containers by adding it to the container's config. :)
Fuse support would enable the use of gocryptfs, which would be very useful for me.
> You can simply tell LXD to load the kernel module by setting

Unfortunately, Fuse not not appear to be in termina's kernel, otherwise you'd be right.  At least, I'm not seeing /dev/fuse.  Something I'm missing?

I've been waiting for this for a while to the point where I've considered enabling developer mode to just add it myself.
FUSE is not enabled in the current termina kernels
re: kernel modules in general, we have set CONFIG_MODULES=n so no modules can be loaded at runtime.

Unprivileged fuse mounts should be enabled in 4.18, so we can look at this more closely after the next CrOS kernel rebase.
Labels: M-72
Owner: smbar...@chromium.org
Status: Started (was: Available)
We have 4.19 now, so this turned out to be as easy as flipping the kernel config and adding /dev/fuse to tremplin.

This might need libfuse 3.0 to work, which isn't in Debian stretch. But I was able to build and mount the hello world example from libfuse master, so we'll at least be ready when buster comes around.
M72 feature freeze technically was last week, so seems like M73 material
Labels: -M-72 M-73
Project Member

Comment 14 by bugdroid1@chromium.org, Dec 2

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/platform/tremplin/+/a937be0b3f412059e34c068f3cf47bd1873bfb8c

commit a937be0b3f412059e34c068f3cf47bd1873bfb8c
Author: Stephen Barber <smbarber@chromium.org>
Date: Sun Dec 02 02:21:03 2018

tremplin: add FUSE character device

BUG= chromium:841787 
TEST=/dev/fuse has mode 0666, root:root in container
CQ-DEPEND=CL:1334035

Change-Id: Id3e8b9e885ca2c7ebb8fab7933d14025d76d8703
Reviewed-on: https://chromium-review.googlesource.com/1334042
Commit-Ready: Stephen Barber <smbarber@chromium.org>
Tested-by: Stephen Barber <smbarber@chromium.org>
Reviewed-by: Chirantan Ekbote <chirantan@chromium.org>

[modify] https://crrev.com/a937be0b3f412059e34c068f3cf47bd1873bfb8c/src/chromiumos/tremplin/main.go

Project Member

Comment 15 by bugdroid1@chromium.org, Dec 2

Labels: merge-merged-chromeos-4.19
The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/b0ec11c21bbde638f64b322f376569da44af72dd

commit b0ec11c21bbde638f64b322f376569da44af72dd
Author: Stephen Barber <smbarber@chromium.org>
Date: Sun Dec 02 02:21:02 2018

CHROMIUM: arch: configs: enable FUSE for VMs

Signed-off-by: Stephen Barber <smbarber@chromium.org>

BUG= chromium:841787 
TEST=/dev/fuse exists in VM

Change-Id: I26f2690096ad5b96eef11819fb2fb7bc712865a7
Reviewed-on: https://chromium-review.googlesource.com/1334035
Commit-Ready: Stephen Barber <smbarber@chromium.org>
Tested-by: Stephen Barber <smbarber@chromium.org>
Reviewed-by: Zach Reizner <zachr@chromium.org>

[modify] https://crrev.com/b0ec11c21bbde638f64b322f376569da44af72dd/arch/arm64/configs/chromiumos-container-vm-arm64_defconfig
[modify] https://crrev.com/b0ec11c21bbde638f64b322f376569da44af72dd/arch/x86/configs/chromiumos-container-vm-x86_64_defconfig

Status: Fixed (was: Started)
can you update the FAQ ?  i think we should mention the release it's available in, and the min version of the fuse client that they'd need (since, iirc, the default one in the container today is too old).
Project Member

Comment 18 by bugdroid1@chromium.org, Jan 17 (5 days ago)

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/docs/+/3e8987dcae7afb324c020729dd6056c4f0423af8

commit 3e8987dcae7afb324c020729dd6056c4f0423af8
Author: Stephen Barber <smbarber@chromium.org>
Date: Thu Jan 17 23:56:49 2019

containers_and_vms: update FUSE FAQ

FUSE is now supported on M73.

BUG= chromium:841787 
TEST=gitiles

Change-Id: Ieaea308018699f4d7db144b7ebadf4c956a9aa8d
Reviewed-on: https://chromium-review.googlesource.com/1416597
Commit-Ready: Stephen Barber <smbarber@chromium.org>
Tested-by: Stephen Barber <smbarber@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>

[modify] https://crrev.com/3e8987dcae7afb324c020729dd6056c4f0423af8/containers_and_vms.md

Comment 19 by smbarber@google.com, Jan 18 (5 days ago)

Status: Verified (was: Fixed)
Verified on 73.

Sign in to add a comment