SELinux: restorecon wont change context to httpd_sys_content_tHow do I remove any SELinux context or...

Why is commutativity optional in multiplication for rings?

How to mitigate "bandwagon attacking" from players?

Metadata API deployments are failing in Spring '19

Can a hotel cancel a confirmed reservation?

Does Windows 10's telemetry include sending *.doc files if Word crashed?

Can I become debt free or should I file for bankruptcy? How do I manage my debt and finances?

Do authors have to be politically correct in article-writing?

For Loop and Sum

On what did Lego base the appearance of the new Hogwarts minifigs?

Meaning of すきっとした

Why can I easily sing or whistle a tune I've just heard, but not as easily reproduce it on an instrument?

If I delete my router's history can my ISP still provide it to my parents?

ip vs ifconfig commands pros and cons

Walking in a rotating spacecraft and Newton's 3rd Law of Motion

Where was Karl Mordo in Infinity War?

Why does the DC-9-80 have this cusp in its fuselage?

Finding an integral using a table?

Is my plan for fixing my water heater leak bad?

What is the wife of a henpecked husband called?

LTSpice: When running a linear AC simulation, how to view the voltage ratio between two voltages?

raspberry pi change directory (cd) command not working with USB drive

Can chords be played on the flute?

Counting monomials in skew-symmetric+diagonal matrices

Do commercial flights continue with an engine out?



SELinux: restorecon wont change context to httpd_sys_content_t


How do I remove any SELinux context or ACL?Disable SELinux contextSticky Bit and SELinuxSelinux what's the right context for module like imagemagick /usr/bin/convertsemanage command not changing file contextSelinux deny root userSELinux remove extended ACLHow do I change security context on a directory in CentOS with SELinux?chmodding files with an SELinux security context / ACLHow to mount iso file with selinux context













0















I need to use Puppeteer on a Centos 7.4.1708 system but when I have SELinux set to Enforcing I'm getting AVC errors.



If I run sudo cat /var/log/messages I get:



SELinux is preventing /var/www/html/node_modules/puppeteer/.local-chromium/linux-549031/chrome-linux/chrome from search access on the directory /sys/fs/cgroup/cpuset.

***** Plugin restorecon_source (99.5 confidence) suggests *****************

If you want to fix the label.
/var/www/html/node_modules/puppeteer/.local-chromium/linux-549031/chrome-linux/chrome default label should be httpd_sys_content_t.
Then you can run restorecon.
Do
# /sbin/restorecon -v /var/www/html/node_modules/puppeteer/.local-chromium/linux-549031/chrome-linux/chrome


This same message appears maybe 6 or 7 times.



When I try to do the above though, restorecon won't set the context of the file.



Set policy (as root):
semanage fcontext -a -t httpd_sys_content_t '/var/www/html/node_modules/puppeteer/.local-chromium/linux-549031/chrome-linux/chrome'



Check policy:
matchpathcon /var/www/html/node_modules/puppeteer/.local-chromium/linux-549031/chrome-linux/chrome

Shows:
/var/www/html/node_modules/puppeteer/.local-chromium/linux-549031/chrome-linux/chrome system_u:object_r:httpd_sys_content_t:s0



That looks good, but then...

Set new context to file:
/sbin/restorecon -v /var/www/html/node_modules/puppeteer/.local-chromium/linux-549031/chrome-linux/chrome



restorecon fails to work. I don't get any errors from it even if I use -vv.
I have also tried to force restorecon with -F but that doesn't work either.



Here's the files current context:
ls -Z /var/www/html/node_modules/puppeteer/.local-chromium/linux-549031/chrome-linux/chrome
Shows:
-rwxrwxrwx. root root system_u:object_r:nfs_t:s0 /var/www/html/node_modules/puppeteer/.local-chromium/linux-549031/chrome-linux/chrome



The current context is nfs_t because I use synced folders with nfs in Vagrant running virtual box. I can't change to smb because it doesn't sync both ways using a Windows host.



Any ideas on how I can fix this issue? I've been at it for nearly two days now.



Note: If I set SELinux to Permissive then Puppeteer/Chromium runs without issue.



Thanks :)



Edit: I also should mention I have httpd_use_nfs set to on.



Here's a pastebin of all my SELinux booleans.



SELinux booleans



Edit 2:



Using the advice of @HBruijn I try to mount with defined context, but receive error.



AS root command:
mount 10.0.0.1:/C/Users/Lee/Desktop/www /var/www -o context="system_u:object_r:httpd_sys_content_t:s0"



Error:
mount.nfs: requested NFS version or transport protocol is not supported



Server 10.0.0.1 is my private server setup in vagrantfile.
config.vm.network "private_network", ip: "10.0.0.0"



The export path is the same path Vagrant uses when it mounts a folder on vagrant up e.g 10.0.0.1:/C/path/to/directory.



Any ideas??










share|improve this question















migrated from serverfault.com May 7 '18 at 12:15


This question came from our site for system and network administrators.























    0















    I need to use Puppeteer on a Centos 7.4.1708 system but when I have SELinux set to Enforcing I'm getting AVC errors.



    If I run sudo cat /var/log/messages I get:



    SELinux is preventing /var/www/html/node_modules/puppeteer/.local-chromium/linux-549031/chrome-linux/chrome from search access on the directory /sys/fs/cgroup/cpuset.

    ***** Plugin restorecon_source (99.5 confidence) suggests *****************

    If you want to fix the label.
    /var/www/html/node_modules/puppeteer/.local-chromium/linux-549031/chrome-linux/chrome default label should be httpd_sys_content_t.
    Then you can run restorecon.
    Do
    # /sbin/restorecon -v /var/www/html/node_modules/puppeteer/.local-chromium/linux-549031/chrome-linux/chrome


    This same message appears maybe 6 or 7 times.



    When I try to do the above though, restorecon won't set the context of the file.



    Set policy (as root):
    semanage fcontext -a -t httpd_sys_content_t '/var/www/html/node_modules/puppeteer/.local-chromium/linux-549031/chrome-linux/chrome'



    Check policy:
    matchpathcon /var/www/html/node_modules/puppeteer/.local-chromium/linux-549031/chrome-linux/chrome

    Shows:
    /var/www/html/node_modules/puppeteer/.local-chromium/linux-549031/chrome-linux/chrome system_u:object_r:httpd_sys_content_t:s0



    That looks good, but then...

    Set new context to file:
    /sbin/restorecon -v /var/www/html/node_modules/puppeteer/.local-chromium/linux-549031/chrome-linux/chrome



    restorecon fails to work. I don't get any errors from it even if I use -vv.
    I have also tried to force restorecon with -F but that doesn't work either.



    Here's the files current context:
    ls -Z /var/www/html/node_modules/puppeteer/.local-chromium/linux-549031/chrome-linux/chrome
    Shows:
    -rwxrwxrwx. root root system_u:object_r:nfs_t:s0 /var/www/html/node_modules/puppeteer/.local-chromium/linux-549031/chrome-linux/chrome



    The current context is nfs_t because I use synced folders with nfs in Vagrant running virtual box. I can't change to smb because it doesn't sync both ways using a Windows host.



    Any ideas on how I can fix this issue? I've been at it for nearly two days now.



    Note: If I set SELinux to Permissive then Puppeteer/Chromium runs without issue.



    Thanks :)



    Edit: I also should mention I have httpd_use_nfs set to on.



    Here's a pastebin of all my SELinux booleans.



    SELinux booleans



    Edit 2:



    Using the advice of @HBruijn I try to mount with defined context, but receive error.



    AS root command:
    mount 10.0.0.1:/C/Users/Lee/Desktop/www /var/www -o context="system_u:object_r:httpd_sys_content_t:s0"



    Error:
    mount.nfs: requested NFS version or transport protocol is not supported



    Server 10.0.0.1 is my private server setup in vagrantfile.
    config.vm.network "private_network", ip: "10.0.0.0"



    The export path is the same path Vagrant uses when it mounts a folder on vagrant up e.g 10.0.0.1:/C/path/to/directory.



    Any ideas??










    share|improve this question















    migrated from serverfault.com May 7 '18 at 12:15


    This question came from our site for system and network administrators.





















      0












      0








      0








      I need to use Puppeteer on a Centos 7.4.1708 system but when I have SELinux set to Enforcing I'm getting AVC errors.



      If I run sudo cat /var/log/messages I get:



      SELinux is preventing /var/www/html/node_modules/puppeteer/.local-chromium/linux-549031/chrome-linux/chrome from search access on the directory /sys/fs/cgroup/cpuset.

      ***** Plugin restorecon_source (99.5 confidence) suggests *****************

      If you want to fix the label.
      /var/www/html/node_modules/puppeteer/.local-chromium/linux-549031/chrome-linux/chrome default label should be httpd_sys_content_t.
      Then you can run restorecon.
      Do
      # /sbin/restorecon -v /var/www/html/node_modules/puppeteer/.local-chromium/linux-549031/chrome-linux/chrome


      This same message appears maybe 6 or 7 times.



      When I try to do the above though, restorecon won't set the context of the file.



      Set policy (as root):
      semanage fcontext -a -t httpd_sys_content_t '/var/www/html/node_modules/puppeteer/.local-chromium/linux-549031/chrome-linux/chrome'



      Check policy:
      matchpathcon /var/www/html/node_modules/puppeteer/.local-chromium/linux-549031/chrome-linux/chrome

      Shows:
      /var/www/html/node_modules/puppeteer/.local-chromium/linux-549031/chrome-linux/chrome system_u:object_r:httpd_sys_content_t:s0



      That looks good, but then...

      Set new context to file:
      /sbin/restorecon -v /var/www/html/node_modules/puppeteer/.local-chromium/linux-549031/chrome-linux/chrome



      restorecon fails to work. I don't get any errors from it even if I use -vv.
      I have also tried to force restorecon with -F but that doesn't work either.



      Here's the files current context:
      ls -Z /var/www/html/node_modules/puppeteer/.local-chromium/linux-549031/chrome-linux/chrome
      Shows:
      -rwxrwxrwx. root root system_u:object_r:nfs_t:s0 /var/www/html/node_modules/puppeteer/.local-chromium/linux-549031/chrome-linux/chrome



      The current context is nfs_t because I use synced folders with nfs in Vagrant running virtual box. I can't change to smb because it doesn't sync both ways using a Windows host.



      Any ideas on how I can fix this issue? I've been at it for nearly two days now.



      Note: If I set SELinux to Permissive then Puppeteer/Chromium runs without issue.



      Thanks :)



      Edit: I also should mention I have httpd_use_nfs set to on.



      Here's a pastebin of all my SELinux booleans.



      SELinux booleans



      Edit 2:



      Using the advice of @HBruijn I try to mount with defined context, but receive error.



      AS root command:
      mount 10.0.0.1:/C/Users/Lee/Desktop/www /var/www -o context="system_u:object_r:httpd_sys_content_t:s0"



      Error:
      mount.nfs: requested NFS version or transport protocol is not supported



      Server 10.0.0.1 is my private server setup in vagrantfile.
      config.vm.network "private_network", ip: "10.0.0.0"



      The export path is the same path Vagrant uses when it mounts a folder on vagrant up e.g 10.0.0.1:/C/path/to/directory.



      Any ideas??










      share|improve this question
















      I need to use Puppeteer on a Centos 7.4.1708 system but when I have SELinux set to Enforcing I'm getting AVC errors.



      If I run sudo cat /var/log/messages I get:



      SELinux is preventing /var/www/html/node_modules/puppeteer/.local-chromium/linux-549031/chrome-linux/chrome from search access on the directory /sys/fs/cgroup/cpuset.

      ***** Plugin restorecon_source (99.5 confidence) suggests *****************

      If you want to fix the label.
      /var/www/html/node_modules/puppeteer/.local-chromium/linux-549031/chrome-linux/chrome default label should be httpd_sys_content_t.
      Then you can run restorecon.
      Do
      # /sbin/restorecon -v /var/www/html/node_modules/puppeteer/.local-chromium/linux-549031/chrome-linux/chrome


      This same message appears maybe 6 or 7 times.



      When I try to do the above though, restorecon won't set the context of the file.



      Set policy (as root):
      semanage fcontext -a -t httpd_sys_content_t '/var/www/html/node_modules/puppeteer/.local-chromium/linux-549031/chrome-linux/chrome'



      Check policy:
      matchpathcon /var/www/html/node_modules/puppeteer/.local-chromium/linux-549031/chrome-linux/chrome

      Shows:
      /var/www/html/node_modules/puppeteer/.local-chromium/linux-549031/chrome-linux/chrome system_u:object_r:httpd_sys_content_t:s0



      That looks good, but then...

      Set new context to file:
      /sbin/restorecon -v /var/www/html/node_modules/puppeteer/.local-chromium/linux-549031/chrome-linux/chrome



      restorecon fails to work. I don't get any errors from it even if I use -vv.
      I have also tried to force restorecon with -F but that doesn't work either.



      Here's the files current context:
      ls -Z /var/www/html/node_modules/puppeteer/.local-chromium/linux-549031/chrome-linux/chrome
      Shows:
      -rwxrwxrwx. root root system_u:object_r:nfs_t:s0 /var/www/html/node_modules/puppeteer/.local-chromium/linux-549031/chrome-linux/chrome



      The current context is nfs_t because I use synced folders with nfs in Vagrant running virtual box. I can't change to smb because it doesn't sync both ways using a Windows host.



      Any ideas on how I can fix this issue? I've been at it for nearly two days now.



      Note: If I set SELinux to Permissive then Puppeteer/Chromium runs without issue.



      Thanks :)



      Edit: I also should mention I have httpd_use_nfs set to on.



      Here's a pastebin of all my SELinux booleans.



      SELinux booleans



      Edit 2:



      Using the advice of @HBruijn I try to mount with defined context, but receive error.



      AS root command:
      mount 10.0.0.1:/C/Users/Lee/Desktop/www /var/www -o context="system_u:object_r:httpd_sys_content_t:s0"



      Error:
      mount.nfs: requested NFS version or transport protocol is not supported



      Server 10.0.0.1 is my private server setup in vagrantfile.
      config.vm.network "private_network", ip: "10.0.0.0"



      The export path is the same path Vagrant uses when it mounts a folder on vagrant up e.g 10.0.0.1:/C/path/to/directory.



      Any ideas??







      linux selinux






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited May 8 '18 at 14:47







      turrican_34

















      asked May 7 '18 at 11:41









      turrican_34turrican_34

      105




      105




      migrated from serverfault.com May 7 '18 at 12:15


      This question came from our site for system and network administrators.









      migrated from serverfault.com May 7 '18 at 12:15


      This question came from our site for system and network administrators.
























          2 Answers
          2






          active

          oldest

          votes


















          0














          I think you're trying to solve the problem from the wrong end, have you considered giving your webserver access to NFS shares instead with:



          setsebool -P httpd_use_nfs=1 


          EDIT Based on your comment that you running VirtualBox on Windows:



          I think that your Windows host does not support labeling and then the client (your CentOS) assigns a default security policy as nfs_t.



          You may need to set your preferred security context as a mount option to override that default (in the mount command or /etc/fstab) :



          # mount server:/export /var/www/html -o  context="system_u:object_r:httpd_sys_content_t:s0" 


          See the RHEL 6 manual






          share|improve this answer


























          • Sorry, I forgot to mention that I already have httpd_use_nfs --> on. I'll edit the OP.

            – turrican_34
            May 7 '18 at 11:56











          • I've added a pastebin of all my other SELinux booleans.

            – turrican_34
            May 7 '18 at 12:08











          • Am I correct in understanding that you are running VirtualBox on Windows with a CentOS guest OS?

            – HBruijn
            May 7 '18 at 12:11











          • Yes, thats correct. Using the winnfsd plugin to get nfs working in windows.

            – turrican_34
            May 7 '18 at 12:14











          • When I run that as root I get this error: mount.nfs: Failed to resolve server server: Name or service not known mount.nfs: Operation already in progress

            – turrican_34
            May 7 '18 at 12:36





















          0














          Try setting below options with mount. They worked for me in CIFS mount. Might work on nfs too.
          uid=
          gid=
          file_mode=
          dir_mode=
          fscontext=





          share























            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "3"
            };
            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: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            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%2fsuperuser.com%2fquestions%2f1320442%2fselinux-restorecon-wont-change-context-to-httpd-sys-content-t%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            2 Answers
            2






            active

            oldest

            votes








            2 Answers
            2






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            I think you're trying to solve the problem from the wrong end, have you considered giving your webserver access to NFS shares instead with:



            setsebool -P httpd_use_nfs=1 


            EDIT Based on your comment that you running VirtualBox on Windows:



            I think that your Windows host does not support labeling and then the client (your CentOS) assigns a default security policy as nfs_t.



            You may need to set your preferred security context as a mount option to override that default (in the mount command or /etc/fstab) :



            # mount server:/export /var/www/html -o  context="system_u:object_r:httpd_sys_content_t:s0" 


            See the RHEL 6 manual






            share|improve this answer


























            • Sorry, I forgot to mention that I already have httpd_use_nfs --> on. I'll edit the OP.

              – turrican_34
              May 7 '18 at 11:56











            • I've added a pastebin of all my other SELinux booleans.

              – turrican_34
              May 7 '18 at 12:08











            • Am I correct in understanding that you are running VirtualBox on Windows with a CentOS guest OS?

              – HBruijn
              May 7 '18 at 12:11











            • Yes, thats correct. Using the winnfsd plugin to get nfs working in windows.

              – turrican_34
              May 7 '18 at 12:14











            • When I run that as root I get this error: mount.nfs: Failed to resolve server server: Name or service not known mount.nfs: Operation already in progress

              – turrican_34
              May 7 '18 at 12:36


















            0














            I think you're trying to solve the problem from the wrong end, have you considered giving your webserver access to NFS shares instead with:



            setsebool -P httpd_use_nfs=1 


            EDIT Based on your comment that you running VirtualBox on Windows:



            I think that your Windows host does not support labeling and then the client (your CentOS) assigns a default security policy as nfs_t.



            You may need to set your preferred security context as a mount option to override that default (in the mount command or /etc/fstab) :



            # mount server:/export /var/www/html -o  context="system_u:object_r:httpd_sys_content_t:s0" 


            See the RHEL 6 manual






            share|improve this answer


























            • Sorry, I forgot to mention that I already have httpd_use_nfs --> on. I'll edit the OP.

              – turrican_34
              May 7 '18 at 11:56











            • I've added a pastebin of all my other SELinux booleans.

              – turrican_34
              May 7 '18 at 12:08











            • Am I correct in understanding that you are running VirtualBox on Windows with a CentOS guest OS?

              – HBruijn
              May 7 '18 at 12:11











            • Yes, thats correct. Using the winnfsd plugin to get nfs working in windows.

              – turrican_34
              May 7 '18 at 12:14











            • When I run that as root I get this error: mount.nfs: Failed to resolve server server: Name or service not known mount.nfs: Operation already in progress

              – turrican_34
              May 7 '18 at 12:36
















            0












            0








            0







            I think you're trying to solve the problem from the wrong end, have you considered giving your webserver access to NFS shares instead with:



            setsebool -P httpd_use_nfs=1 


            EDIT Based on your comment that you running VirtualBox on Windows:



            I think that your Windows host does not support labeling and then the client (your CentOS) assigns a default security policy as nfs_t.



            You may need to set your preferred security context as a mount option to override that default (in the mount command or /etc/fstab) :



            # mount server:/export /var/www/html -o  context="system_u:object_r:httpd_sys_content_t:s0" 


            See the RHEL 6 manual






            share|improve this answer















            I think you're trying to solve the problem from the wrong end, have you considered giving your webserver access to NFS shares instead with:



            setsebool -P httpd_use_nfs=1 


            EDIT Based on your comment that you running VirtualBox on Windows:



            I think that your Windows host does not support labeling and then the client (your CentOS) assigns a default security policy as nfs_t.



            You may need to set your preferred security context as a mount option to override that default (in the mount command or /etc/fstab) :



            # mount server:/export /var/www/html -o  context="system_u:object_r:httpd_sys_content_t:s0" 


            See the RHEL 6 manual







            share|improve this answer














            share|improve this answer



            share|improve this answer








            edited May 7 '18 at 12:22

























            answered May 7 '18 at 11:52









            HBruijnHBruijn

            83949




            83949













            • Sorry, I forgot to mention that I already have httpd_use_nfs --> on. I'll edit the OP.

              – turrican_34
              May 7 '18 at 11:56











            • I've added a pastebin of all my other SELinux booleans.

              – turrican_34
              May 7 '18 at 12:08











            • Am I correct in understanding that you are running VirtualBox on Windows with a CentOS guest OS?

              – HBruijn
              May 7 '18 at 12:11











            • Yes, thats correct. Using the winnfsd plugin to get nfs working in windows.

              – turrican_34
              May 7 '18 at 12:14











            • When I run that as root I get this error: mount.nfs: Failed to resolve server server: Name or service not known mount.nfs: Operation already in progress

              – turrican_34
              May 7 '18 at 12:36





















            • Sorry, I forgot to mention that I already have httpd_use_nfs --> on. I'll edit the OP.

              – turrican_34
              May 7 '18 at 11:56











            • I've added a pastebin of all my other SELinux booleans.

              – turrican_34
              May 7 '18 at 12:08











            • Am I correct in understanding that you are running VirtualBox on Windows with a CentOS guest OS?

              – HBruijn
              May 7 '18 at 12:11











            • Yes, thats correct. Using the winnfsd plugin to get nfs working in windows.

              – turrican_34
              May 7 '18 at 12:14











            • When I run that as root I get this error: mount.nfs: Failed to resolve server server: Name or service not known mount.nfs: Operation already in progress

              – turrican_34
              May 7 '18 at 12:36



















            Sorry, I forgot to mention that I already have httpd_use_nfs --> on. I'll edit the OP.

            – turrican_34
            May 7 '18 at 11:56





            Sorry, I forgot to mention that I already have httpd_use_nfs --> on. I'll edit the OP.

            – turrican_34
            May 7 '18 at 11:56













            I've added a pastebin of all my other SELinux booleans.

            – turrican_34
            May 7 '18 at 12:08





            I've added a pastebin of all my other SELinux booleans.

            – turrican_34
            May 7 '18 at 12:08













            Am I correct in understanding that you are running VirtualBox on Windows with a CentOS guest OS?

            – HBruijn
            May 7 '18 at 12:11





            Am I correct in understanding that you are running VirtualBox on Windows with a CentOS guest OS?

            – HBruijn
            May 7 '18 at 12:11













            Yes, thats correct. Using the winnfsd plugin to get nfs working in windows.

            – turrican_34
            May 7 '18 at 12:14





            Yes, thats correct. Using the winnfsd plugin to get nfs working in windows.

            – turrican_34
            May 7 '18 at 12:14













            When I run that as root I get this error: mount.nfs: Failed to resolve server server: Name or service not known mount.nfs: Operation already in progress

            – turrican_34
            May 7 '18 at 12:36







            When I run that as root I get this error: mount.nfs: Failed to resolve server server: Name or service not known mount.nfs: Operation already in progress

            – turrican_34
            May 7 '18 at 12:36















            0














            Try setting below options with mount. They worked for me in CIFS mount. Might work on nfs too.
            uid=
            gid=
            file_mode=
            dir_mode=
            fscontext=





            share




























              0














              Try setting below options with mount. They worked for me in CIFS mount. Might work on nfs too.
              uid=
              gid=
              file_mode=
              dir_mode=
              fscontext=





              share


























                0












                0








                0







                Try setting below options with mount. They worked for me in CIFS mount. Might work on nfs too.
                uid=
                gid=
                file_mode=
                dir_mode=
                fscontext=





                share













                Try setting below options with mount. They worked for me in CIFS mount. Might work on nfs too.
                uid=
                gid=
                file_mode=
                dir_mode=
                fscontext=






                share











                share


                share










                answered 7 mins ago









                Lolitha RatnayakeLolitha Ratnayake

                1314




                1314






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Super User!


                    • 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%2fsuperuser.com%2fquestions%2f1320442%2fselinux-restorecon-wont-change-context-to-httpd-sys-content-t%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

                    Couldn't open a raw socket. Error: Permission denied (13) (nmap)Is it possible to run networking commands...

                    VNC viewer RFB protocol error: bad desktop size 0x0I Cannot Type the Key 'd' (lowercase) in VNC Viewer...

                    Why not use the yoke to control yaw, as well as pitch and roll? Announcing the arrival of...