“VBoxManage not found. Make sure VirtualBox is installed and VBoxManage is in the path”












1















I'm getting the error:



Error with pre-create check: "VBoxManage not found. Make sure VirtualBox is installed and VBoxManage is in the path"



When trying to create a vm in terminal. I've uninstalled and reinstalled virtualbox, Ive confirmed VBoxManage exists.










share|improve this question
















bumped to the homepage by Community 14 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
















  • Can you check the output of which VBoxManage or type VBoxManage from the same terminal?

    – Haxiel
    Nov 20 '18 at 6:22











  • Output of 'type VboxManage' is VBoxManage is /usr/bin/VBoxManage. Output of 'which VBoxManage' was nothing.

    – MellOhNoctis
    Nov 20 '18 at 20:22













  • Actually the output for 'which VBoxManage' was: /usr/bin/VBoxManage

    – MellOhNoctis
    Nov 20 '18 at 23:12











  • Please edit the question to add information instead of answering the comments directly. Have you tried running the VBoxManage command with sudo/root?

    – Haxiel
    Nov 21 '18 at 8:21













  • Editing the question with the answer was rejected. But I have also tried with sudo/root.

    – MellOhNoctis
    Nov 25 '18 at 23:22
















1















I'm getting the error:



Error with pre-create check: "VBoxManage not found. Make sure VirtualBox is installed and VBoxManage is in the path"



When trying to create a vm in terminal. I've uninstalled and reinstalled virtualbox, Ive confirmed VBoxManage exists.










share|improve this question
















bumped to the homepage by Community 14 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
















  • Can you check the output of which VBoxManage or type VBoxManage from the same terminal?

    – Haxiel
    Nov 20 '18 at 6:22











  • Output of 'type VboxManage' is VBoxManage is /usr/bin/VBoxManage. Output of 'which VBoxManage' was nothing.

    – MellOhNoctis
    Nov 20 '18 at 20:22













  • Actually the output for 'which VBoxManage' was: /usr/bin/VBoxManage

    – MellOhNoctis
    Nov 20 '18 at 23:12











  • Please edit the question to add information instead of answering the comments directly. Have you tried running the VBoxManage command with sudo/root?

    – Haxiel
    Nov 21 '18 at 8:21













  • Editing the question with the answer was rejected. But I have also tried with sudo/root.

    – MellOhNoctis
    Nov 25 '18 at 23:22














1












1








1








I'm getting the error:



Error with pre-create check: "VBoxManage not found. Make sure VirtualBox is installed and VBoxManage is in the path"



When trying to create a vm in terminal. I've uninstalled and reinstalled virtualbox, Ive confirmed VBoxManage exists.










share|improve this question
















I'm getting the error:



Error with pre-create check: "VBoxManage not found. Make sure VirtualBox is installed and VBoxManage is in the path"



When trying to create a vm in terminal. I've uninstalled and reinstalled virtualbox, Ive confirmed VBoxManage exists.







linux virtualbox docker






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 20 '18 at 6:26









Rui F Ribeiro

40.2k1479135




40.2k1479135










asked Nov 20 '18 at 4:13









MellOhNoctisMellOhNoctis

62




62





bumped to the homepage by Community 14 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







bumped to the homepage by Community 14 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.















  • Can you check the output of which VBoxManage or type VBoxManage from the same terminal?

    – Haxiel
    Nov 20 '18 at 6:22











  • Output of 'type VboxManage' is VBoxManage is /usr/bin/VBoxManage. Output of 'which VBoxManage' was nothing.

    – MellOhNoctis
    Nov 20 '18 at 20:22













  • Actually the output for 'which VBoxManage' was: /usr/bin/VBoxManage

    – MellOhNoctis
    Nov 20 '18 at 23:12











  • Please edit the question to add information instead of answering the comments directly. Have you tried running the VBoxManage command with sudo/root?

    – Haxiel
    Nov 21 '18 at 8:21













  • Editing the question with the answer was rejected. But I have also tried with sudo/root.

    – MellOhNoctis
    Nov 25 '18 at 23:22



















  • Can you check the output of which VBoxManage or type VBoxManage from the same terminal?

    – Haxiel
    Nov 20 '18 at 6:22











  • Output of 'type VboxManage' is VBoxManage is /usr/bin/VBoxManage. Output of 'which VBoxManage' was nothing.

    – MellOhNoctis
    Nov 20 '18 at 20:22













  • Actually the output for 'which VBoxManage' was: /usr/bin/VBoxManage

    – MellOhNoctis
    Nov 20 '18 at 23:12











  • Please edit the question to add information instead of answering the comments directly. Have you tried running the VBoxManage command with sudo/root?

    – Haxiel
    Nov 21 '18 at 8:21













  • Editing the question with the answer was rejected. But I have also tried with sudo/root.

    – MellOhNoctis
    Nov 25 '18 at 23:22

















Can you check the output of which VBoxManage or type VBoxManage from the same terminal?

– Haxiel
Nov 20 '18 at 6:22





Can you check the output of which VBoxManage or type VBoxManage from the same terminal?

– Haxiel
Nov 20 '18 at 6:22













Output of 'type VboxManage' is VBoxManage is /usr/bin/VBoxManage. Output of 'which VBoxManage' was nothing.

– MellOhNoctis
Nov 20 '18 at 20:22







Output of 'type VboxManage' is VBoxManage is /usr/bin/VBoxManage. Output of 'which VBoxManage' was nothing.

– MellOhNoctis
Nov 20 '18 at 20:22















Actually the output for 'which VBoxManage' was: /usr/bin/VBoxManage

– MellOhNoctis
Nov 20 '18 at 23:12





Actually the output for 'which VBoxManage' was: /usr/bin/VBoxManage

– MellOhNoctis
Nov 20 '18 at 23:12













Please edit the question to add information instead of answering the comments directly. Have you tried running the VBoxManage command with sudo/root?

– Haxiel
Nov 21 '18 at 8:21







Please edit the question to add information instead of answering the comments directly. Have you tried running the VBoxManage command with sudo/root?

– Haxiel
Nov 21 '18 at 8:21















Editing the question with the answer was rejected. But I have also tried with sudo/root.

– MellOhNoctis
Nov 25 '18 at 23:22





Editing the question with the answer was rejected. But I have also tried with sudo/root.

– MellOhNoctis
Nov 25 '18 at 23:22










1 Answer
1






active

oldest

votes


















0














Had the same issue on ubuntu 18.04, had installed docker using snap
i removed that and installed docker and docker-compse using apt
and docker-machine using

$ base=https://github.com/docker/machine/releases/download/v0.16.0 &&
curl -L $base/docker-machine-$(uname -s)-$(uname -m) >/tmp/docker-machine &&
sudo install /tmp/docker-machine /usr/local/bin/docker-machine

difference is snap will install docker-machine v0.15 and we will be installing v0.16






share|improve this answer























    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%2f482880%2fvboxmanage-not-found-make-sure-virtualbox-is-installed-and-vboxmanage-is-in-th%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









    0














    Had the same issue on ubuntu 18.04, had installed docker using snap
    i removed that and installed docker and docker-compse using apt
    and docker-machine using

    $ base=https://github.com/docker/machine/releases/download/v0.16.0 &&
    curl -L $base/docker-machine-$(uname -s)-$(uname -m) >/tmp/docker-machine &&
    sudo install /tmp/docker-machine /usr/local/bin/docker-machine

    difference is snap will install docker-machine v0.15 and we will be installing v0.16






    share|improve this answer




























      0














      Had the same issue on ubuntu 18.04, had installed docker using snap
      i removed that and installed docker and docker-compse using apt
      and docker-machine using

      $ base=https://github.com/docker/machine/releases/download/v0.16.0 &&
      curl -L $base/docker-machine-$(uname -s)-$(uname -m) >/tmp/docker-machine &&
      sudo install /tmp/docker-machine /usr/local/bin/docker-machine

      difference is snap will install docker-machine v0.15 and we will be installing v0.16






      share|improve this answer


























        0












        0








        0







        Had the same issue on ubuntu 18.04, had installed docker using snap
        i removed that and installed docker and docker-compse using apt
        and docker-machine using

        $ base=https://github.com/docker/machine/releases/download/v0.16.0 &&
        curl -L $base/docker-machine-$(uname -s)-$(uname -m) >/tmp/docker-machine &&
        sudo install /tmp/docker-machine /usr/local/bin/docker-machine

        difference is snap will install docker-machine v0.15 and we will be installing v0.16






        share|improve this answer













        Had the same issue on ubuntu 18.04, had installed docker using snap
        i removed that and installed docker and docker-compse using apt
        and docker-machine using

        $ base=https://github.com/docker/machine/releases/download/v0.16.0 &&
        curl -L $base/docker-machine-$(uname -s)-$(uname -m) >/tmp/docker-machine &&
        sudo install /tmp/docker-machine /usr/local/bin/docker-machine

        difference is snap will install docker-machine v0.15 and we will be installing v0.16







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Dec 10 '18 at 12:14









        Parvez ShahParvez Shah

        1




        1






























            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.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f482880%2fvboxmanage-not-found-make-sure-virtualbox-is-installed-and-vboxmanage-is-in-th%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

            Loup dans la culture

            How to solve the problem of ntp “Unable to contact time server” from KDE?

            ASUS Zenbook UX433/UX333 — Configure Touchpad-embedded numpad on Linux