Error installing Visual Studio Code as snapwhat does this skype message mean?Uninstall Visual Studio Code...

Why Were Madagascar and New Zealand Discovered So Late?

How do I extract a value from a time formatted value in excel?

How can I kill an app using Terminal?

Return the Closest Prime Number

Is the destination of a commercial flight important for the pilot?

How does it work when somebody invests in my business?

India just shot down a satellite from the ground. At what altitude range is the resulting debris field?

How did Doctor Strange see the winning outcome in Avengers: Infinity War?

Detecting if an element is found inside a container

How to be diplomatic in refusing to write code that breaches the privacy of our users

How long to clear the 'suck zone' of a turbofan after start is initiated?

Hostile work environment after whistle-blowing on coworker and our boss. What do I do?

How to Reset Passwords on Multiple Websites Easily?

What is the difference between "behavior" and "behaviour"?

Why, precisely, is argon used in neutrino experiments?

Why didn't Theresa May consult with Parliament before negotiating a deal with the EU?

Class Action - which options I have?

Is exact Kanji stroke length important?

Inappropriate reference requests from Journal reviewers

Sequence of Tenses: Translating the subjunctive

Is there a korbon needed for conversion?

Pre-amplifier input protection

What happens if you roll doubles 3 times then land on "Go to jail?"

Failed to fetch jessie backports repository



Error installing Visual Studio Code as snap


what does this skype message mean?Uninstall Visual Studio Code 32bitVisual Studio Code sometimes wont loadVisual Studio code not installing in ubuntu 16.04?Using ironpython in Visual studio codeCannot open Visual Studio CodeFacing problems while installing Visual Studio Code on Ubuntu 18.04Visual studio code can't runVisual Studio Code wont launch after installingvisual studio code menu bar not visible in ubuntu18.10Lunch visual studio code show black screen













7















I tried to install MS Visual Studio Code as snap on Ubuntu 16.04 with the following command:



sudo snap install vscode


but I've got the following error:



error: This revision of snap "vscode" was published using classic confinement and thus may perform
arbitrary system changes outside of the security sandbox that snaps are usually confined to,
which put your system at risk.

If you understand and want to proceed repeat the command including --classic.


I'd like to know what does --classic flag do (not just man page explanation) and why did I get the previous error while I was installing Visual Studio Code.










share|improve this question























  • I've tried installing it via snap (with --classic), but snap reports error: cannot install "vscode": snap not found. Were you able to install it?

    – Drunken Master
    May 20 '17 at 21:23
















7















I tried to install MS Visual Studio Code as snap on Ubuntu 16.04 with the following command:



sudo snap install vscode


but I've got the following error:



error: This revision of snap "vscode" was published using classic confinement and thus may perform
arbitrary system changes outside of the security sandbox that snaps are usually confined to,
which put your system at risk.

If you understand and want to proceed repeat the command including --classic.


I'd like to know what does --classic flag do (not just man page explanation) and why did I get the previous error while I was installing Visual Studio Code.










share|improve this question























  • I've tried installing it via snap (with --classic), but snap reports error: cannot install "vscode": snap not found. Were you able to install it?

    – Drunken Master
    May 20 '17 at 21:23














7












7








7








I tried to install MS Visual Studio Code as snap on Ubuntu 16.04 with the following command:



sudo snap install vscode


but I've got the following error:



error: This revision of snap "vscode" was published using classic confinement and thus may perform
arbitrary system changes outside of the security sandbox that snaps are usually confined to,
which put your system at risk.

If you understand and want to proceed repeat the command including --classic.


I'd like to know what does --classic flag do (not just man page explanation) and why did I get the previous error while I was installing Visual Studio Code.










share|improve this question














I tried to install MS Visual Studio Code as snap on Ubuntu 16.04 with the following command:



sudo snap install vscode


but I've got the following error:



error: This revision of snap "vscode" was published using classic confinement and thus may perform
arbitrary system changes outside of the security sandbox that snaps are usually confined to,
which put your system at risk.

If you understand and want to proceed repeat the command including --classic.


I'd like to know what does --classic flag do (not just man page explanation) and why did I get the previous error while I was installing Visual Studio Code.







snap visual-studio-code






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked May 20 '17 at 8:35









DanibixDanibix

1,45111122




1,45111122













  • I've tried installing it via snap (with --classic), but snap reports error: cannot install "vscode": snap not found. Were you able to install it?

    – Drunken Master
    May 20 '17 at 21:23



















  • I've tried installing it via snap (with --classic), but snap reports error: cannot install "vscode": snap not found. Were you able to install it?

    – Drunken Master
    May 20 '17 at 21:23

















I've tried installing it via snap (with --classic), but snap reports error: cannot install "vscode": snap not found. Were you able to install it?

– Drunken Master
May 20 '17 at 21:23





I've tried installing it via snap (with --classic), but snap reports error: cannot install "vscode": snap not found. Were you able to install it?

– Drunken Master
May 20 '17 at 21:23










1 Answer
1






active

oldest

votes


















5














Watch this short video that explains each of the confinement models available in snaps, why --classic exists and it's use case.





Sources: The following documentation is taken from snapcraft.io: confinement policies.



strict



This is the default security policy applied to snaps. The snap has read and/or write rights only in its own install space and selected areas. It has access to libraries it bundles and/or provided by the core or ubuntu-core snap. Extended rights can be granted with interfaces, which are connected either at install time or by the user with the snap connect command. For example, the home interface will grant read rights in the user’s home.



Strict confinement gives you the following readable and/or writable paths:




  • /snap/snapname/revision (read-only, snap install path)

  • /var/snap/snapname/revision (read/write, per-revision data)

  • /var/snap/snapname/common (read/write, common data)

  • /home/$USER/snap/snapname/revision (read/write, per-revision user data)

  • /home/$USER/snap/snapname/common (read/write, common user data)


See the list of environment variables for more details on what is visible to a strictly confined snap, as well as ways to access a shell within the confined space of a snap.



devmode



Developer mode, also known as devmode, uses the same security policies as strict confinement, but security denials are turned into warnings in /var/log/syslog (see Debugging). This is useful when snapping an application, to discover which interfaces need to be declared. Snaps in developer mode can not be released into the stable and candidate store channels.



classic



A snap in classic confinement behaves as a traditionally packaged application, with full access to the system. As opposed to strict and devmode, what a classic snap sees as “/” is the host system’s “/” and not the core snap’s “/”. Snaps using this fully open security policy are manually reviewed in the store and are only allowed on systems where snapd is installed on top of a traditional Linux distribution, as opposed to system booting from an Ubuntu Core image. They can be released in all store channels.






share|improve this answer

























    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "89"
    };
    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%2faskubuntu.com%2fquestions%2f917049%2ferror-installing-visual-studio-code-as-snap%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









    5














    Watch this short video that explains each of the confinement models available in snaps, why --classic exists and it's use case.





    Sources: The following documentation is taken from snapcraft.io: confinement policies.



    strict



    This is the default security policy applied to snaps. The snap has read and/or write rights only in its own install space and selected areas. It has access to libraries it bundles and/or provided by the core or ubuntu-core snap. Extended rights can be granted with interfaces, which are connected either at install time or by the user with the snap connect command. For example, the home interface will grant read rights in the user’s home.



    Strict confinement gives you the following readable and/or writable paths:




    • /snap/snapname/revision (read-only, snap install path)

    • /var/snap/snapname/revision (read/write, per-revision data)

    • /var/snap/snapname/common (read/write, common data)

    • /home/$USER/snap/snapname/revision (read/write, per-revision user data)

    • /home/$USER/snap/snapname/common (read/write, common user data)


    See the list of environment variables for more details on what is visible to a strictly confined snap, as well as ways to access a shell within the confined space of a snap.



    devmode



    Developer mode, also known as devmode, uses the same security policies as strict confinement, but security denials are turned into warnings in /var/log/syslog (see Debugging). This is useful when snapping an application, to discover which interfaces need to be declared. Snaps in developer mode can not be released into the stable and candidate store channels.



    classic



    A snap in classic confinement behaves as a traditionally packaged application, with full access to the system. As opposed to strict and devmode, what a classic snap sees as “/” is the host system’s “/” and not the core snap’s “/”. Snaps using this fully open security policy are manually reviewed in the store and are only allowed on systems where snapd is installed on top of a traditional Linux distribution, as opposed to system booting from an Ubuntu Core image. They can be released in all store channels.






    share|improve this answer






























      5














      Watch this short video that explains each of the confinement models available in snaps, why --classic exists and it's use case.





      Sources: The following documentation is taken from snapcraft.io: confinement policies.



      strict



      This is the default security policy applied to snaps. The snap has read and/or write rights only in its own install space and selected areas. It has access to libraries it bundles and/or provided by the core or ubuntu-core snap. Extended rights can be granted with interfaces, which are connected either at install time or by the user with the snap connect command. For example, the home interface will grant read rights in the user’s home.



      Strict confinement gives you the following readable and/or writable paths:




      • /snap/snapname/revision (read-only, snap install path)

      • /var/snap/snapname/revision (read/write, per-revision data)

      • /var/snap/snapname/common (read/write, common data)

      • /home/$USER/snap/snapname/revision (read/write, per-revision user data)

      • /home/$USER/snap/snapname/common (read/write, common user data)


      See the list of environment variables for more details on what is visible to a strictly confined snap, as well as ways to access a shell within the confined space of a snap.



      devmode



      Developer mode, also known as devmode, uses the same security policies as strict confinement, but security denials are turned into warnings in /var/log/syslog (see Debugging). This is useful when snapping an application, to discover which interfaces need to be declared. Snaps in developer mode can not be released into the stable and candidate store channels.



      classic



      A snap in classic confinement behaves as a traditionally packaged application, with full access to the system. As opposed to strict and devmode, what a classic snap sees as “/” is the host system’s “/” and not the core snap’s “/”. Snaps using this fully open security policy are manually reviewed in the store and are only allowed on systems where snapd is installed on top of a traditional Linux distribution, as opposed to system booting from an Ubuntu Core image. They can be released in all store channels.






      share|improve this answer




























        5












        5








        5







        Watch this short video that explains each of the confinement models available in snaps, why --classic exists and it's use case.





        Sources: The following documentation is taken from snapcraft.io: confinement policies.



        strict



        This is the default security policy applied to snaps. The snap has read and/or write rights only in its own install space and selected areas. It has access to libraries it bundles and/or provided by the core or ubuntu-core snap. Extended rights can be granted with interfaces, which are connected either at install time or by the user with the snap connect command. For example, the home interface will grant read rights in the user’s home.



        Strict confinement gives you the following readable and/or writable paths:




        • /snap/snapname/revision (read-only, snap install path)

        • /var/snap/snapname/revision (read/write, per-revision data)

        • /var/snap/snapname/common (read/write, common data)

        • /home/$USER/snap/snapname/revision (read/write, per-revision user data)

        • /home/$USER/snap/snapname/common (read/write, common user data)


        See the list of environment variables for more details on what is visible to a strictly confined snap, as well as ways to access a shell within the confined space of a snap.



        devmode



        Developer mode, also known as devmode, uses the same security policies as strict confinement, but security denials are turned into warnings in /var/log/syslog (see Debugging). This is useful when snapping an application, to discover which interfaces need to be declared. Snaps in developer mode can not be released into the stable and candidate store channels.



        classic



        A snap in classic confinement behaves as a traditionally packaged application, with full access to the system. As opposed to strict and devmode, what a classic snap sees as “/” is the host system’s “/” and not the core snap’s “/”. Snaps using this fully open security policy are manually reviewed in the store and are only allowed on systems where snapd is installed on top of a traditional Linux distribution, as opposed to system booting from an Ubuntu Core image. They can be released in all store channels.






        share|improve this answer















        Watch this short video that explains each of the confinement models available in snaps, why --classic exists and it's use case.





        Sources: The following documentation is taken from snapcraft.io: confinement policies.



        strict



        This is the default security policy applied to snaps. The snap has read and/or write rights only in its own install space and selected areas. It has access to libraries it bundles and/or provided by the core or ubuntu-core snap. Extended rights can be granted with interfaces, which are connected either at install time or by the user with the snap connect command. For example, the home interface will grant read rights in the user’s home.



        Strict confinement gives you the following readable and/or writable paths:




        • /snap/snapname/revision (read-only, snap install path)

        • /var/snap/snapname/revision (read/write, per-revision data)

        • /var/snap/snapname/common (read/write, common data)

        • /home/$USER/snap/snapname/revision (read/write, per-revision user data)

        • /home/$USER/snap/snapname/common (read/write, common user data)


        See the list of environment variables for more details on what is visible to a strictly confined snap, as well as ways to access a shell within the confined space of a snap.



        devmode



        Developer mode, also known as devmode, uses the same security policies as strict confinement, but security denials are turned into warnings in /var/log/syslog (see Debugging). This is useful when snapping an application, to discover which interfaces need to be declared. Snaps in developer mode can not be released into the stable and candidate store channels.



        classic



        A snap in classic confinement behaves as a traditionally packaged application, with full access to the system. As opposed to strict and devmode, what a classic snap sees as “/” is the host system’s “/” and not the core snap’s “/”. Snaps using this fully open security policy are manually reviewed in the store and are only allowed on systems where snapd is installed on top of a traditional Linux distribution, as opposed to system booting from an Ubuntu Core image. They can be released in all store channels.







        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited 17 mins ago









        Pablo Bianchi

        3,02021536




        3,02021536










        answered May 20 '17 at 9:59









        Martin WimpressMartin Wimpress

        54238




        54238






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Ask Ubuntu!


            • 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%2faskubuntu.com%2fquestions%2f917049%2ferror-installing-visual-studio-code-as-snap%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

            Why do type traits not work with types in namespace scope?What are POD types in C++?Why can templates only be...

            Will tsunami waves travel forever if there was no land?Why do tsunami waves begin with the water flowing away...

            Should I use Docker or LXD?How to cache (more) data on SSD/RAM to avoid spin up?Unable to get Windows File...