How to convert an existing VirtualBox virtual machine to Image?How can I get multiple virtual machines to...

Is it possible that the shadow of the moon is a single dot during solar eclipse?

Degenerate Gaussian Integral

Wrong Schengen Visa exit stamp on my passport, who can I complain to?

How often is duct tape used during crewed space missions?

Persuading players to be less attached to a pre-session 0 character concept

Is there a generally agreed upon solution to Bradley's Infinite Regress without appeal to Paraconsistent Logic?

In Bb5 systems against the Sicilian, why does White exchange their b5 bishop without playing a6?

Neta Revai is achzareyos?

What does “We have long ago paid the goblins of Moria,” from The Hobbit mean?

How do we know that black holes are spinning?

Why don't airports use arresting gears to recover energy from landing passenger planes?

What is a "major country" as named in Bernie Sanders' Healthcare debate answers?

Anagrams Question

Beauville-Laszlo for schemes

What is the difference between an engine skirt and an engine nozzle?

What does the "capacitor into resistance" symbol mean?

What does the Free Recovery sign (UK) actually mean?

Is there a theorem in Real analysis similar to Cauchy's theorem in Complex analysis?

Python web-scraper to download table of transistor counts from Wikipedia

How can I draw overlapping triangles?

Permutations in Disguise

Who are the people reviewing far more papers than they're submitting for review?

Other than good shoes and a stick, what are some ways to preserve your knees on long hikes?

Can an infinite series be thought of as adding up "infinitely many" terms?



How to convert an existing VirtualBox virtual machine to Image?


How can I get multiple virtual machines to communicate on the same network using VirtualBox and Ubuntu 16.04?How would I edit Vagrantfile so that Vagrant knows to get the .box file from my host?Migrating a Virtualbox virtual machine into a physical dual-boot systemPentesting from a virtual machine, hiding the hostResize of VirtualBox Screen?SSH to a virtual machineUSB not working : USB Ports Hijacked/Reserved Permanently by VirtualBoxHow do I adjust the screen resolution for my Debian 8.1 64-bit VirtualBox machine?How to diagnose, why Linux Mint host freezes after starting Virtualbox VMHow to get the same network with QEMU than VirtualBoxvirtualbox: how to allocate memory from swapRepair possible file system corruption in virtual Linux guest OS (Virtualbox)






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}







1















Suppose I install an ISO of Linux Mint as a virtual machine on VirtualBox.



I want to install several programs, such as Terminator, Netbeans, Java, Ruby on Rails, etc.



How can I convert the virtual machine back to ISO so when I install on any other physical computer I have already my programs working as I configured?










share|improve this question



























  • You have not defined wether installing in another computer is physical or another vbox, or how many times you are replicating the image

    – Rui F Ribeiro
    Jul 28 '18 at 14:07













  • It's to be installed in a physical computer

    – Aleksandrus
    Jul 28 '18 at 14:33











  • If it were several computers, I would point you out to vagrant+packer

    – Rui F Ribeiro
    Jul 28 '18 at 14:34


















1















Suppose I install an ISO of Linux Mint as a virtual machine on VirtualBox.



I want to install several programs, such as Terminator, Netbeans, Java, Ruby on Rails, etc.



How can I convert the virtual machine back to ISO so when I install on any other physical computer I have already my programs working as I configured?










share|improve this question



























  • You have not defined wether installing in another computer is physical or another vbox, or how many times you are replicating the image

    – Rui F Ribeiro
    Jul 28 '18 at 14:07













  • It's to be installed in a physical computer

    – Aleksandrus
    Jul 28 '18 at 14:33











  • If it were several computers, I would point you out to vagrant+packer

    – Rui F Ribeiro
    Jul 28 '18 at 14:34














1












1








1








Suppose I install an ISO of Linux Mint as a virtual machine on VirtualBox.



I want to install several programs, such as Terminator, Netbeans, Java, Ruby on Rails, etc.



How can I convert the virtual machine back to ISO so when I install on any other physical computer I have already my programs working as I configured?










share|improve this question
















Suppose I install an ISO of Linux Mint as a virtual machine on VirtualBox.



I want to install several programs, such as Terminator, Netbeans, Java, Ruby on Rails, etc.



How can I convert the virtual machine back to ISO so when I install on any other physical computer I have already my programs working as I configured?







linux virtualbox virtual-machine






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jul 28 '18 at 14:33







Aleksandrus

















asked Jul 27 '18 at 15:30









AleksandrusAleksandrus

1611 silver badge8 bronze badges




1611 silver badge8 bronze badges
















  • You have not defined wether installing in another computer is physical or another vbox, or how many times you are replicating the image

    – Rui F Ribeiro
    Jul 28 '18 at 14:07













  • It's to be installed in a physical computer

    – Aleksandrus
    Jul 28 '18 at 14:33











  • If it were several computers, I would point you out to vagrant+packer

    – Rui F Ribeiro
    Jul 28 '18 at 14:34



















  • You have not defined wether installing in another computer is physical or another vbox, or how many times you are replicating the image

    – Rui F Ribeiro
    Jul 28 '18 at 14:07













  • It's to be installed in a physical computer

    – Aleksandrus
    Jul 28 '18 at 14:33











  • If it were several computers, I would point you out to vagrant+packer

    – Rui F Ribeiro
    Jul 28 '18 at 14:34

















You have not defined wether installing in another computer is physical or another vbox, or how many times you are replicating the image

– Rui F Ribeiro
Jul 28 '18 at 14:07







You have not defined wether installing in another computer is physical or another vbox, or how many times you are replicating the image

– Rui F Ribeiro
Jul 28 '18 at 14:07















It's to be installed in a physical computer

– Aleksandrus
Jul 28 '18 at 14:33





It's to be installed in a physical computer

– Aleksandrus
Jul 28 '18 at 14:33













If it were several computers, I would point you out to vagrant+packer

– Rui F Ribeiro
Jul 28 '18 at 14:34





If it were several computers, I would point you out to vagrant+packer

– Rui F Ribeiro
Jul 28 '18 at 14:34










2 Answers
2






active

oldest

votes


















1
















I would not do it that way.



Debian, Ubuntu, Mint, etc



If you are using Debian or derivatives (e.g. mint), then have a look at equivs-control. It is a stupidly named tool, to allow you to make your own deb packages, so long as they only have dependencies (it is easier that making more general debs). You then only need to install this one package on all of your machines, and it will the other packages to be installed.



There are also tools to allow you to build Debian based ISO/Usb images, that are same as standard, but some extra packages pre-installed.



Any




  • Write a shell script.

  • Or use configuration management.






share|improve this answer



































    1
















    Vagrant



    I like using Vagrant to do this type of customization. You can either use the stock CentOS/Ubuntu/Debian box files (.box) as initial base boxes or you can start with a stock ISO and build your own Vagrant box file using it.



    The .box files that most will typically want to use are here:




    • centos/7

    • ubuntu/xenial64

    • debian/jessie64

    • or more...


    Example



    Now take one of the sample Vagrantfiles:



    $ cat Vagrantfile
    Vagrant.configure("2") do |config|
    config.vm.box = "centos/7"
    end


    or you can use one of mine via my github.com vagrantfiles repo. Now start it up, and SSH into it:



    $ vagrant up
    $ vagrant ssh


    Once in, customize it. Once you're done exit the VM. Now you can package it:



    $ vagrant package --base my-centos7


    Once this is done, you'll get a .box file. This .box file can be referenced in other Vagrantfiles for further reuse.



    Managing .box files



    If you just want to download a .box file you can use vagrant to do this like so:



    $ vagrant box add centos/7


    See vagrant box for additional usage details.



    References




    • Creating a Base Box

    • How would I edit Vagrantfile so that Vagrant knows to get the .box file from my host?

    • How can I get multiple virtual machines to communicate on the same network using VirtualBox and Ubuntu 16.04?






    share|improve this answer




























    • Did you make an error in paragraph 1? You say start with a stock system, or with a stock system.

      – ctrl-alt-delor
      Jul 28 '18 at 9:34











    • @ctrl-alt-delor nope. You can start with the vagrant cloud box files which are stock builds from canonical, CentOS, Debian projects, or build your own using the iso. I'll elaborate that paragraph

      – slm
      Jul 28 '18 at 11:57














    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/4.0/"u003ecc by-sa 4.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%2f458875%2fhow-to-convert-an-existing-virtualbox-virtual-machine-to-image%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









    1
















    I would not do it that way.



    Debian, Ubuntu, Mint, etc



    If you are using Debian or derivatives (e.g. mint), then have a look at equivs-control. It is a stupidly named tool, to allow you to make your own deb packages, so long as they only have dependencies (it is easier that making more general debs). You then only need to install this one package on all of your machines, and it will the other packages to be installed.



    There are also tools to allow you to build Debian based ISO/Usb images, that are same as standard, but some extra packages pre-installed.



    Any




    • Write a shell script.

    • Or use configuration management.






    share|improve this answer
































      1
















      I would not do it that way.



      Debian, Ubuntu, Mint, etc



      If you are using Debian or derivatives (e.g. mint), then have a look at equivs-control. It is a stupidly named tool, to allow you to make your own deb packages, so long as they only have dependencies (it is easier that making more general debs). You then only need to install this one package on all of your machines, and it will the other packages to be installed.



      There are also tools to allow you to build Debian based ISO/Usb images, that are same as standard, but some extra packages pre-installed.



      Any




      • Write a shell script.

      • Or use configuration management.






      share|improve this answer






























        1














        1










        1









        I would not do it that way.



        Debian, Ubuntu, Mint, etc



        If you are using Debian or derivatives (e.g. mint), then have a look at equivs-control. It is a stupidly named tool, to allow you to make your own deb packages, so long as they only have dependencies (it is easier that making more general debs). You then only need to install this one package on all of your machines, and it will the other packages to be installed.



        There are also tools to allow you to build Debian based ISO/Usb images, that are same as standard, but some extra packages pre-installed.



        Any




        • Write a shell script.

        • Or use configuration management.






        share|improve this answer















        I would not do it that way.



        Debian, Ubuntu, Mint, etc



        If you are using Debian or derivatives (e.g. mint), then have a look at equivs-control. It is a stupidly named tool, to allow you to make your own deb packages, so long as they only have dependencies (it is easier that making more general debs). You then only need to install this one package on all of your machines, and it will the other packages to be installed.



        There are also tools to allow you to build Debian based ISO/Usb images, that are same as standard, but some extra packages pre-installed.



        Any




        • Write a shell script.

        • Or use configuration management.







        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited Jul 28 '18 at 9:32

























        answered Jul 27 '18 at 16:15









        ctrl-alt-delorctrl-alt-delor

        14.3k6 gold badges33 silver badges64 bronze badges




        14.3k6 gold badges33 silver badges64 bronze badges




























            1
















            Vagrant



            I like using Vagrant to do this type of customization. You can either use the stock CentOS/Ubuntu/Debian box files (.box) as initial base boxes or you can start with a stock ISO and build your own Vagrant box file using it.



            The .box files that most will typically want to use are here:




            • centos/7

            • ubuntu/xenial64

            • debian/jessie64

            • or more...


            Example



            Now take one of the sample Vagrantfiles:



            $ cat Vagrantfile
            Vagrant.configure("2") do |config|
            config.vm.box = "centos/7"
            end


            or you can use one of mine via my github.com vagrantfiles repo. Now start it up, and SSH into it:



            $ vagrant up
            $ vagrant ssh


            Once in, customize it. Once you're done exit the VM. Now you can package it:



            $ vagrant package --base my-centos7


            Once this is done, you'll get a .box file. This .box file can be referenced in other Vagrantfiles for further reuse.



            Managing .box files



            If you just want to download a .box file you can use vagrant to do this like so:



            $ vagrant box add centos/7


            See vagrant box for additional usage details.



            References




            • Creating a Base Box

            • How would I edit Vagrantfile so that Vagrant knows to get the .box file from my host?

            • How can I get multiple virtual machines to communicate on the same network using VirtualBox and Ubuntu 16.04?






            share|improve this answer




























            • Did you make an error in paragraph 1? You say start with a stock system, or with a stock system.

              – ctrl-alt-delor
              Jul 28 '18 at 9:34











            • @ctrl-alt-delor nope. You can start with the vagrant cloud box files which are stock builds from canonical, CentOS, Debian projects, or build your own using the iso. I'll elaborate that paragraph

              – slm
              Jul 28 '18 at 11:57
















            1
















            Vagrant



            I like using Vagrant to do this type of customization. You can either use the stock CentOS/Ubuntu/Debian box files (.box) as initial base boxes or you can start with a stock ISO and build your own Vagrant box file using it.



            The .box files that most will typically want to use are here:




            • centos/7

            • ubuntu/xenial64

            • debian/jessie64

            • or more...


            Example



            Now take one of the sample Vagrantfiles:



            $ cat Vagrantfile
            Vagrant.configure("2") do |config|
            config.vm.box = "centos/7"
            end


            or you can use one of mine via my github.com vagrantfiles repo. Now start it up, and SSH into it:



            $ vagrant up
            $ vagrant ssh


            Once in, customize it. Once you're done exit the VM. Now you can package it:



            $ vagrant package --base my-centos7


            Once this is done, you'll get a .box file. This .box file can be referenced in other Vagrantfiles for further reuse.



            Managing .box files



            If you just want to download a .box file you can use vagrant to do this like so:



            $ vagrant box add centos/7


            See vagrant box for additional usage details.



            References




            • Creating a Base Box

            • How would I edit Vagrantfile so that Vagrant knows to get the .box file from my host?

            • How can I get multiple virtual machines to communicate on the same network using VirtualBox and Ubuntu 16.04?






            share|improve this answer




























            • Did you make an error in paragraph 1? You say start with a stock system, or with a stock system.

              – ctrl-alt-delor
              Jul 28 '18 at 9:34











            • @ctrl-alt-delor nope. You can start with the vagrant cloud box files which are stock builds from canonical, CentOS, Debian projects, or build your own using the iso. I'll elaborate that paragraph

              – slm
              Jul 28 '18 at 11:57














            1














            1










            1









            Vagrant



            I like using Vagrant to do this type of customization. You can either use the stock CentOS/Ubuntu/Debian box files (.box) as initial base boxes or you can start with a stock ISO and build your own Vagrant box file using it.



            The .box files that most will typically want to use are here:




            • centos/7

            • ubuntu/xenial64

            • debian/jessie64

            • or more...


            Example



            Now take one of the sample Vagrantfiles:



            $ cat Vagrantfile
            Vagrant.configure("2") do |config|
            config.vm.box = "centos/7"
            end


            or you can use one of mine via my github.com vagrantfiles repo. Now start it up, and SSH into it:



            $ vagrant up
            $ vagrant ssh


            Once in, customize it. Once you're done exit the VM. Now you can package it:



            $ vagrant package --base my-centos7


            Once this is done, you'll get a .box file. This .box file can be referenced in other Vagrantfiles for further reuse.



            Managing .box files



            If you just want to download a .box file you can use vagrant to do this like so:



            $ vagrant box add centos/7


            See vagrant box for additional usage details.



            References




            • Creating a Base Box

            • How would I edit Vagrantfile so that Vagrant knows to get the .box file from my host?

            • How can I get multiple virtual machines to communicate on the same network using VirtualBox and Ubuntu 16.04?






            share|improve this answer















            Vagrant



            I like using Vagrant to do this type of customization. You can either use the stock CentOS/Ubuntu/Debian box files (.box) as initial base boxes or you can start with a stock ISO and build your own Vagrant box file using it.



            The .box files that most will typically want to use are here:




            • centos/7

            • ubuntu/xenial64

            • debian/jessie64

            • or more...


            Example



            Now take one of the sample Vagrantfiles:



            $ cat Vagrantfile
            Vagrant.configure("2") do |config|
            config.vm.box = "centos/7"
            end


            or you can use one of mine via my github.com vagrantfiles repo. Now start it up, and SSH into it:



            $ vagrant up
            $ vagrant ssh


            Once in, customize it. Once you're done exit the VM. Now you can package it:



            $ vagrant package --base my-centos7


            Once this is done, you'll get a .box file. This .box file can be referenced in other Vagrantfiles for further reuse.



            Managing .box files



            If you just want to download a .box file you can use vagrant to do this like so:



            $ vagrant box add centos/7


            See vagrant box for additional usage details.



            References




            • Creating a Base Box

            • How would I edit Vagrantfile so that Vagrant knows to get the .box file from my host?

            • How can I get multiple virtual machines to communicate on the same network using VirtualBox and Ubuntu 16.04?







            share|improve this answer














            share|improve this answer



            share|improve this answer








            edited 1 hour ago









            Pang

            2072 silver badges7 bronze badges




            2072 silver badges7 bronze badges










            answered Jul 28 '18 at 0:59









            slmslm

            269k75 gold badges582 silver badges728 bronze badges




            269k75 gold badges582 silver badges728 bronze badges
















            • Did you make an error in paragraph 1? You say start with a stock system, or with a stock system.

              – ctrl-alt-delor
              Jul 28 '18 at 9:34











            • @ctrl-alt-delor nope. You can start with the vagrant cloud box files which are stock builds from canonical, CentOS, Debian projects, or build your own using the iso. I'll elaborate that paragraph

              – slm
              Jul 28 '18 at 11:57



















            • Did you make an error in paragraph 1? You say start with a stock system, or with a stock system.

              – ctrl-alt-delor
              Jul 28 '18 at 9:34











            • @ctrl-alt-delor nope. You can start with the vagrant cloud box files which are stock builds from canonical, CentOS, Debian projects, or build your own using the iso. I'll elaborate that paragraph

              – slm
              Jul 28 '18 at 11:57

















            Did you make an error in paragraph 1? You say start with a stock system, or with a stock system.

            – ctrl-alt-delor
            Jul 28 '18 at 9:34





            Did you make an error in paragraph 1? You say start with a stock system, or with a stock system.

            – ctrl-alt-delor
            Jul 28 '18 at 9:34













            @ctrl-alt-delor nope. You can start with the vagrant cloud box files which are stock builds from canonical, CentOS, Debian projects, or build your own using the iso. I'll elaborate that paragraph

            – slm
            Jul 28 '18 at 11:57





            @ctrl-alt-delor nope. You can start with the vagrant cloud box files which are stock builds from canonical, CentOS, Debian projects, or build your own using the iso. I'll elaborate that paragraph

            – slm
            Jul 28 '18 at 11:57



















            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%2f458875%2fhow-to-convert-an-existing-virtualbox-virtual-machine-to-image%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

            Taj Mahal Inhaltsverzeichnis Aufbau | Geschichte | 350-Jahr-Feier | Heutige Bedeutung | Siehe auch |...

            Baia Sprie Cuprins Etimologie | Istorie | Demografie | Politică și administrație | Arii naturale...

            Nicolae Petrescu-Găină Cuprins Biografie | Opera | In memoriam | Varia | Controverse, incertitudini...