Travis build failing on “The SUID sandbox helper binary was found, but…”











up vote
0
down vote

favorite












My Angular app tests are passing locally, however they are failing on travis with the following error:




The SUID sandbox helper binary was found, but is not configured
correctly. Rather than run without sandboxing I'm aborting now. You
need to make sure that /opt/google/chrome/chrome-sandbox is owned by
root and has mode 4755.











share|improve this question


























    up vote
    0
    down vote

    favorite












    My Angular app tests are passing locally, however they are failing on travis with the following error:




    The SUID sandbox helper binary was found, but is not configured
    correctly. Rather than run without sandboxing I'm aborting now. You
    need to make sure that /opt/google/chrome/chrome-sandbox is owned by
    root and has mode 4755.











    share|improve this question
























      up vote
      0
      down vote

      favorite









      up vote
      0
      down vote

      favorite











      My Angular app tests are passing locally, however they are failing on travis with the following error:




      The SUID sandbox helper binary was found, but is not configured
      correctly. Rather than run without sandboxing I'm aborting now. You
      need to make sure that /opt/google/chrome/chrome-sandbox is owned by
      root and has mode 4755.











      share|improve this question













      My Angular app tests are passing locally, however they are failing on travis with the following error:




      The SUID sandbox helper binary was found, but is not configured
      correctly. Rather than run without sandboxing I'm aborting now. You
      need to make sure that /opt/google/chrome/chrome-sandbox is owned by
      root and has mode 4755.








      angular karma-runner travis-ci google-chrome-headless angular-testing






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 19 at 12:36









      Francesco Borzì

      12.1k74776




      12.1k74776
























          1 Answer
          1






          active

          oldest

          votes

















          up vote
          0
          down vote













          I solve the issue by editing my karma.conf.js file and adding the following object to my customLaunchers:



          ChromeHeadlessNoSandbox: {
          base: 'ChromeHeadless',
          flags: ['--no-sandbox']
          }


          so my karma.conf.js looks like the following:



          module.exports = function (config) {
          config.set({
          // other parameters...
          browsers : [
          'ChromeHeadlessNoSandbox'
          // other browsers (if any)
          ],
          customLaunchers: {
          ChromeHeadlessNoSandbox: {
          base: 'ChromeHeadless',
          flags: ['--no-sandbox']
          }
          // other browsers (if any)
          },
          });
          };


          then I run my test with --browser=ChromeHeadlessNoSandbox






          share|improve this answer





















            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%2f53374818%2ftravis-build-failing-on-the-suid-sandbox-helper-binary-was-found-but%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes








            up vote
            0
            down vote













            I solve the issue by editing my karma.conf.js file and adding the following object to my customLaunchers:



            ChromeHeadlessNoSandbox: {
            base: 'ChromeHeadless',
            flags: ['--no-sandbox']
            }


            so my karma.conf.js looks like the following:



            module.exports = function (config) {
            config.set({
            // other parameters...
            browsers : [
            'ChromeHeadlessNoSandbox'
            // other browsers (if any)
            ],
            customLaunchers: {
            ChromeHeadlessNoSandbox: {
            base: 'ChromeHeadless',
            flags: ['--no-sandbox']
            }
            // other browsers (if any)
            },
            });
            };


            then I run my test with --browser=ChromeHeadlessNoSandbox






            share|improve this answer

























              up vote
              0
              down vote













              I solve the issue by editing my karma.conf.js file and adding the following object to my customLaunchers:



              ChromeHeadlessNoSandbox: {
              base: 'ChromeHeadless',
              flags: ['--no-sandbox']
              }


              so my karma.conf.js looks like the following:



              module.exports = function (config) {
              config.set({
              // other parameters...
              browsers : [
              'ChromeHeadlessNoSandbox'
              // other browsers (if any)
              ],
              customLaunchers: {
              ChromeHeadlessNoSandbox: {
              base: 'ChromeHeadless',
              flags: ['--no-sandbox']
              }
              // other browsers (if any)
              },
              });
              };


              then I run my test with --browser=ChromeHeadlessNoSandbox






              share|improve this answer























                up vote
                0
                down vote










                up vote
                0
                down vote









                I solve the issue by editing my karma.conf.js file and adding the following object to my customLaunchers:



                ChromeHeadlessNoSandbox: {
                base: 'ChromeHeadless',
                flags: ['--no-sandbox']
                }


                so my karma.conf.js looks like the following:



                module.exports = function (config) {
                config.set({
                // other parameters...
                browsers : [
                'ChromeHeadlessNoSandbox'
                // other browsers (if any)
                ],
                customLaunchers: {
                ChromeHeadlessNoSandbox: {
                base: 'ChromeHeadless',
                flags: ['--no-sandbox']
                }
                // other browsers (if any)
                },
                });
                };


                then I run my test with --browser=ChromeHeadlessNoSandbox






                share|improve this answer












                I solve the issue by editing my karma.conf.js file and adding the following object to my customLaunchers:



                ChromeHeadlessNoSandbox: {
                base: 'ChromeHeadless',
                flags: ['--no-sandbox']
                }


                so my karma.conf.js looks like the following:



                module.exports = function (config) {
                config.set({
                // other parameters...
                browsers : [
                'ChromeHeadlessNoSandbox'
                // other browsers (if any)
                ],
                customLaunchers: {
                ChromeHeadlessNoSandbox: {
                base: 'ChromeHeadless',
                flags: ['--no-sandbox']
                }
                // other browsers (if any)
                },
                });
                };


                then I run my test with --browser=ChromeHeadlessNoSandbox







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Nov 19 at 12:36









                Francesco Borzì

                12.1k74776




                12.1k74776






























                     

                    draft saved


                    draft discarded



















































                     


                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53374818%2ftravis-build-failing-on-the-suid-sandbox-helper-binary-was-found-but%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

                    To store a contact into the json file from server.js file using a class in NodeJS

                    Redirect URL with Chrome Remote Debugging Android Devices

                    Dieringhausen