Trouble installing fuse on Debian stretch Docker image

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP












0














I am attempting to fuse a dir in a Docker image using gcsfuse. I am using a Debian stretch image, and having trouble working with the fuse package.



I have attempted to install fuse both via apt-get as well as build from the source via the git repo. Both have had their respective problems.



1: After apt-get I receive indication that fuse was successfully installed.



root@a7d6f712fab9:/queue# apt-get install fuse
Reading package lists... Done
Building dependency tree
Reading state information... Done
fuse is already the newest version (2.9.7-1+deb9u2).
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
root@a7d6f712fab9:/queue# apt-get install libfuse-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
libfuse-dev is already the newest version (2.9.7-1+deb9u2)


However when running modprobe fuse (what fails during the gcsfuse mount attempt):



root@a7d6f712fab9:/queue# modprobe fuse
modprobe: ERROR: ../libkmod/libkmod.c:586 kmod_search_moddep() could not open moddep file '/lib/modules/4.9.125-linuxkit/modules.dep.bin'
modprobe: FATAL: Module fuse not found in directory /lib/modules/4.9.125-linuxkit


2: When using the tar.gz from source, meson is only available as version 0.37, whereas libfuse requires meson > 0.38 to build properly (from earlier versions).



Here's my Dockerfile:



FROM python:3.6-slim

RUN apt-get update
&& apt-get install -y libfuse-dev
curl
gnupg
apt-utils
lsb-release
kmod
RUN export GCSFUSE_REPO=gcsfuse-`lsb_release -c -s`
&& echo "deb http://packages.cloud.google.com/apt $GCSFUSE_REPO main" | tee /etc/apt/sources.list.d/gcsfuse.list
&& curl https://packages.cloud.google.com/apt/doc/apt-key.gpg | apt-key add -
RUN apt-get update
&& apt-get install -y gcsfuse

COPY . /queue
WORKDIR /queue


I'd like modprobe fuse to actually work, or to understand how I can build fuse/modprobe in a way where the package is identified via modprobe.



Thanks!










share|improve this question

















  • 1




    By default docker instances can not load kernel modules. You may be able to remove these restrictions with the --privileged command, but this removes all security.
    – Stephen Harris
    Dec 27 '18 at 4:14










  • Thanks @StephenHarris, I was able to resolve my issue by giving the container access to the kernel modules.
    – Sillson
    Dec 29 '18 at 0:37















0














I am attempting to fuse a dir in a Docker image using gcsfuse. I am using a Debian stretch image, and having trouble working with the fuse package.



I have attempted to install fuse both via apt-get as well as build from the source via the git repo. Both have had their respective problems.



1: After apt-get I receive indication that fuse was successfully installed.



root@a7d6f712fab9:/queue# apt-get install fuse
Reading package lists... Done
Building dependency tree
Reading state information... Done
fuse is already the newest version (2.9.7-1+deb9u2).
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
root@a7d6f712fab9:/queue# apt-get install libfuse-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
libfuse-dev is already the newest version (2.9.7-1+deb9u2)


However when running modprobe fuse (what fails during the gcsfuse mount attempt):



root@a7d6f712fab9:/queue# modprobe fuse
modprobe: ERROR: ../libkmod/libkmod.c:586 kmod_search_moddep() could not open moddep file '/lib/modules/4.9.125-linuxkit/modules.dep.bin'
modprobe: FATAL: Module fuse not found in directory /lib/modules/4.9.125-linuxkit


2: When using the tar.gz from source, meson is only available as version 0.37, whereas libfuse requires meson > 0.38 to build properly (from earlier versions).



Here's my Dockerfile:



FROM python:3.6-slim

RUN apt-get update
&& apt-get install -y libfuse-dev
curl
gnupg
apt-utils
lsb-release
kmod
RUN export GCSFUSE_REPO=gcsfuse-`lsb_release -c -s`
&& echo "deb http://packages.cloud.google.com/apt $GCSFUSE_REPO main" | tee /etc/apt/sources.list.d/gcsfuse.list
&& curl https://packages.cloud.google.com/apt/doc/apt-key.gpg | apt-key add -
RUN apt-get update
&& apt-get install -y gcsfuse

COPY . /queue
WORKDIR /queue


I'd like modprobe fuse to actually work, or to understand how I can build fuse/modprobe in a way where the package is identified via modprobe.



Thanks!










share|improve this question

















  • 1




    By default docker instances can not load kernel modules. You may be able to remove these restrictions with the --privileged command, but this removes all security.
    – Stephen Harris
    Dec 27 '18 at 4:14










  • Thanks @StephenHarris, I was able to resolve my issue by giving the container access to the kernel modules.
    – Sillson
    Dec 29 '18 at 0:37













0












0








0







I am attempting to fuse a dir in a Docker image using gcsfuse. I am using a Debian stretch image, and having trouble working with the fuse package.



I have attempted to install fuse both via apt-get as well as build from the source via the git repo. Both have had their respective problems.



1: After apt-get I receive indication that fuse was successfully installed.



root@a7d6f712fab9:/queue# apt-get install fuse
Reading package lists... Done
Building dependency tree
Reading state information... Done
fuse is already the newest version (2.9.7-1+deb9u2).
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
root@a7d6f712fab9:/queue# apt-get install libfuse-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
libfuse-dev is already the newest version (2.9.7-1+deb9u2)


However when running modprobe fuse (what fails during the gcsfuse mount attempt):



root@a7d6f712fab9:/queue# modprobe fuse
modprobe: ERROR: ../libkmod/libkmod.c:586 kmod_search_moddep() could not open moddep file '/lib/modules/4.9.125-linuxkit/modules.dep.bin'
modprobe: FATAL: Module fuse not found in directory /lib/modules/4.9.125-linuxkit


2: When using the tar.gz from source, meson is only available as version 0.37, whereas libfuse requires meson > 0.38 to build properly (from earlier versions).



Here's my Dockerfile:



FROM python:3.6-slim

RUN apt-get update
&& apt-get install -y libfuse-dev
curl
gnupg
apt-utils
lsb-release
kmod
RUN export GCSFUSE_REPO=gcsfuse-`lsb_release -c -s`
&& echo "deb http://packages.cloud.google.com/apt $GCSFUSE_REPO main" | tee /etc/apt/sources.list.d/gcsfuse.list
&& curl https://packages.cloud.google.com/apt/doc/apt-key.gpg | apt-key add -
RUN apt-get update
&& apt-get install -y gcsfuse

COPY . /queue
WORKDIR /queue


I'd like modprobe fuse to actually work, or to understand how I can build fuse/modprobe in a way where the package is identified via modprobe.



Thanks!










share|improve this question













I am attempting to fuse a dir in a Docker image using gcsfuse. I am using a Debian stretch image, and having trouble working with the fuse package.



I have attempted to install fuse both via apt-get as well as build from the source via the git repo. Both have had their respective problems.



1: After apt-get I receive indication that fuse was successfully installed.



root@a7d6f712fab9:/queue# apt-get install fuse
Reading package lists... Done
Building dependency tree
Reading state information... Done
fuse is already the newest version (2.9.7-1+deb9u2).
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
root@a7d6f712fab9:/queue# apt-get install libfuse-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
libfuse-dev is already the newest version (2.9.7-1+deb9u2)


However when running modprobe fuse (what fails during the gcsfuse mount attempt):



root@a7d6f712fab9:/queue# modprobe fuse
modprobe: ERROR: ../libkmod/libkmod.c:586 kmod_search_moddep() could not open moddep file '/lib/modules/4.9.125-linuxkit/modules.dep.bin'
modprobe: FATAL: Module fuse not found in directory /lib/modules/4.9.125-linuxkit


2: When using the tar.gz from source, meson is only available as version 0.37, whereas libfuse requires meson > 0.38 to build properly (from earlier versions).



Here's my Dockerfile:



FROM python:3.6-slim

RUN apt-get update
&& apt-get install -y libfuse-dev
curl
gnupg
apt-utils
lsb-release
kmod
RUN export GCSFUSE_REPO=gcsfuse-`lsb_release -c -s`
&& echo "deb http://packages.cloud.google.com/apt $GCSFUSE_REPO main" | tee /etc/apt/sources.list.d/gcsfuse.list
&& curl https://packages.cloud.google.com/apt/doc/apt-key.gpg | apt-key add -
RUN apt-get update
&& apt-get install -y gcsfuse

COPY . /queue
WORKDIR /queue


I'd like modprobe fuse to actually work, or to understand how I can build fuse/modprobe in a way where the package is identified via modprobe.



Thanks!







linux debian docker fuse modprobe






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Dec 27 '18 at 3:48









SillsonSillson

1




1







  • 1




    By default docker instances can not load kernel modules. You may be able to remove these restrictions with the --privileged command, but this removes all security.
    – Stephen Harris
    Dec 27 '18 at 4:14










  • Thanks @StephenHarris, I was able to resolve my issue by giving the container access to the kernel modules.
    – Sillson
    Dec 29 '18 at 0:37












  • 1




    By default docker instances can not load kernel modules. You may be able to remove these restrictions with the --privileged command, but this removes all security.
    – Stephen Harris
    Dec 27 '18 at 4:14










  • Thanks @StephenHarris, I was able to resolve my issue by giving the container access to the kernel modules.
    – Sillson
    Dec 29 '18 at 0:37







1




1




By default docker instances can not load kernel modules. You may be able to remove these restrictions with the --privileged command, but this removes all security.
– Stephen Harris
Dec 27 '18 at 4:14




By default docker instances can not load kernel modules. You may be able to remove these restrictions with the --privileged command, but this removes all security.
– Stephen Harris
Dec 27 '18 at 4:14












Thanks @StephenHarris, I was able to resolve my issue by giving the container access to the kernel modules.
– Sillson
Dec 29 '18 at 0:37




Thanks @StephenHarris, I was able to resolve my issue by giving the container access to the kernel modules.
– Sillson
Dec 29 '18 at 0:37










0






active

oldest

votes











Your Answer








StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);













draft saved

draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f491066%2ftrouble-installing-fuse-on-debian-stretch-docker-image%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes















draft saved

draft discarded
















































Thanks for contributing an answer to Unix & Linux Stack Exchange!


  • Please be sure to answer the question. Provide details and share your research!

But avoid


  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.





Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


Please pay close attention to the following guidance:


  • Please be sure to answer the question. Provide details and share your research!

But avoid


  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f491066%2ftrouble-installing-fuse-on-debian-stretch-docker-image%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown






Popular posts from this blog

Peggy Mitchell

Palaiologos

The Forum (Inglewood, California)