docker-volume-sshfs causing a lot of “SELinux security alert”s











up vote
1
down vote

favorite












i just finished spinning up a new https://github.com/linuxserver/docker-plex with 3 volumes hosted elsewhere via https://github.com/vieux/docker-volume-sshfs.



It seems to be working, but the initial scan of movies is producing a slew of SELinux security alerts on the machine hosting those volumes and I'm not sure how to provide the necessary permissions to stop those alerts. I tried running the suggested ausearch and semodule commands, but no such luck.



SELinux is preventing worker from create access on the lnk_file com.plexapp.agents.imdb_e6579afe4df5b9216549932ca2cd952e89c2774d.

Plugin: catchall
SELinux denied access requested by worker. It is not expected that this access
is required by worker and this access may signal an intrusion attempt. It is
also possible that the specific version or configuration of the application is
causing it to require additional access.

If you believe that worker should be allowed create access on the com.plexapp.agents.imdb_e6579afe4df5b9216549932ca2cd952e89c2774d lnk_file by default.
You should report this as a bug.
You can generate a local policy module to allow this access.
Allow this access for now by executing:
# ausearch -c 'worker' --raw | audit2allow -M my-worker
# semodule -X 300 -i my-worker.pp









share|improve this question




























    up vote
    1
    down vote

    favorite












    i just finished spinning up a new https://github.com/linuxserver/docker-plex with 3 volumes hosted elsewhere via https://github.com/vieux/docker-volume-sshfs.



    It seems to be working, but the initial scan of movies is producing a slew of SELinux security alerts on the machine hosting those volumes and I'm not sure how to provide the necessary permissions to stop those alerts. I tried running the suggested ausearch and semodule commands, but no such luck.



    SELinux is preventing worker from create access on the lnk_file com.plexapp.agents.imdb_e6579afe4df5b9216549932ca2cd952e89c2774d.

    Plugin: catchall
    SELinux denied access requested by worker. It is not expected that this access
    is required by worker and this access may signal an intrusion attempt. It is
    also possible that the specific version or configuration of the application is
    causing it to require additional access.

    If you believe that worker should be allowed create access on the com.plexapp.agents.imdb_e6579afe4df5b9216549932ca2cd952e89c2774d lnk_file by default.
    You should report this as a bug.
    You can generate a local policy module to allow this access.
    Allow this access for now by executing:
    # ausearch -c 'worker' --raw | audit2allow -M my-worker
    # semodule -X 300 -i my-worker.pp









    share|improve this question


























      up vote
      1
      down vote

      favorite









      up vote
      1
      down vote

      favorite











      i just finished spinning up a new https://github.com/linuxserver/docker-plex with 3 volumes hosted elsewhere via https://github.com/vieux/docker-volume-sshfs.



      It seems to be working, but the initial scan of movies is producing a slew of SELinux security alerts on the machine hosting those volumes and I'm not sure how to provide the necessary permissions to stop those alerts. I tried running the suggested ausearch and semodule commands, but no such luck.



      SELinux is preventing worker from create access on the lnk_file com.plexapp.agents.imdb_e6579afe4df5b9216549932ca2cd952e89c2774d.

      Plugin: catchall
      SELinux denied access requested by worker. It is not expected that this access
      is required by worker and this access may signal an intrusion attempt. It is
      also possible that the specific version or configuration of the application is
      causing it to require additional access.

      If you believe that worker should be allowed create access on the com.plexapp.agents.imdb_e6579afe4df5b9216549932ca2cd952e89c2774d lnk_file by default.
      You should report this as a bug.
      You can generate a local policy module to allow this access.
      Allow this access for now by executing:
      # ausearch -c 'worker' --raw | audit2allow -M my-worker
      # semodule -X 300 -i my-worker.pp









      share|improve this question















      i just finished spinning up a new https://github.com/linuxserver/docker-plex with 3 volumes hosted elsewhere via https://github.com/vieux/docker-volume-sshfs.



      It seems to be working, but the initial scan of movies is producing a slew of SELinux security alerts on the machine hosting those volumes and I'm not sure how to provide the necessary permissions to stop those alerts. I tried running the suggested ausearch and semodule commands, but no such luck.



      SELinux is preventing worker from create access on the lnk_file com.plexapp.agents.imdb_e6579afe4df5b9216549932ca2cd952e89c2774d.

      Plugin: catchall
      SELinux denied access requested by worker. It is not expected that this access
      is required by worker and this access may signal an intrusion attempt. It is
      also possible that the specific version or configuration of the application is
      causing it to require additional access.

      If you believe that worker should be allowed create access on the com.plexapp.agents.imdb_e6579afe4df5b9216549932ca2cd952e89c2774d lnk_file by default.
      You should report this as a bug.
      You can generate a local policy module to allow this access.
      Allow this access for now by executing:
      # ausearch -c 'worker' --raw | audit2allow -M my-worker
      # semodule -X 300 -i my-worker.pp






      docker selinux docker-volume plex






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited 2 days ago

























      asked Nov 10 at 18:19









      swv

      366517




      366517





























          active

          oldest

          votes











          Your Answer






          StackExchange.ifUsing("editor", function () {
          StackExchange.using("externalEditor", function () {
          StackExchange.using("snippets", function () {
          StackExchange.snippets.init();
          });
          });
          }, "code-snippets");

          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "1"
          };
          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',
          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%2fstackoverflow.com%2fquestions%2f53242028%2fdocker-volume-sshfs-causing-a-lot-of-selinux-security-alert-s%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown






























          active

          oldest

          votes













          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes
















           

          draft saved


          draft discarded



















































           


          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53242028%2fdocker-volume-sshfs-causing-a-lot-of-selinux-security-alert-s%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

          Florida Star v. B. J. F.

          Danny Elfman

          Lugert, Oklahoma