How to convert an existing VirtualBox virtual machine to Image?

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;







up vote
1
down vote

favorite












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





















  • 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 at 14:07











  • It's to be installed in a physical computer
    – Aleksandrus
    Jul 28 at 14:33










  • If it were several computers, I would point you out to vagrant+packer
    – Rui F Ribeiro
    Jul 28 at 14:34
















up vote
1
down vote

favorite












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





















  • 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 at 14:07











  • It's to be installed in a physical computer
    – Aleksandrus
    Jul 28 at 14:33










  • If it were several computers, I would point you out to vagrant+packer
    – Rui F Ribeiro
    Jul 28 at 14:34












up vote
1
down vote

favorite









up vote
1
down vote

favorite











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













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








edited Jul 28 at 14:33
























asked Jul 27 at 15:30









Aleksandrus

16117




16117











  • 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 at 14:07











  • It's to be installed in a physical computer
    – Aleksandrus
    Jul 28 at 14:33










  • If it were several computers, I would point you out to vagrant+packer
    – Rui F Ribeiro
    Jul 28 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 at 14:07











  • It's to be installed in a physical computer
    – Aleksandrus
    Jul 28 at 14:33










  • If it were several computers, I would point you out to vagrant+packer
    – Rui F Ribeiro
    Jul 28 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 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 at 14:07













It's to be installed in a physical computer
– Aleksandrus
Jul 28 at 14:33




It's to be installed in a physical computer
– Aleksandrus
Jul 28 at 14:33












If it were several computers, I would point you out to vagrant+packer
– Rui F Ribeiro
Jul 28 at 14:34




If it were several computers, I would point you out to vagrant+packer
– Rui F Ribeiro
Jul 28 at 14:34










2 Answers
2






active

oldest

votes

















up vote
1
down vote













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























  • Thanks! I'll take a look at equivs-control
    – Aleksandrus
    Jul 27 at 16:34

















up vote
1
down vote













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 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 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',
convertImagesToLinks: false,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
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

















2 Answers
2






active

oldest

votes








2 Answers
2






active

oldest

votes









active

oldest

votes






active

oldest

votes








up vote
1
down vote













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























  • Thanks! I'll take a look at equivs-control
    – Aleksandrus
    Jul 27 at 16:34














up vote
1
down vote













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























  • Thanks! I'll take a look at equivs-control
    – Aleksandrus
    Jul 27 at 16:34












up vote
1
down vote










up vote
1
down vote









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 at 9:32


























answered Jul 27 at 16:15









ctrl-alt-delor

8,54031946




8,54031946











  • Thanks! I'll take a look at equivs-control
    – Aleksandrus
    Jul 27 at 16:34
















  • Thanks! I'll take a look at equivs-control
    – Aleksandrus
    Jul 27 at 16:34















Thanks! I'll take a look at equivs-control
– Aleksandrus
Jul 27 at 16:34




Thanks! I'll take a look at equivs-control
– Aleksandrus
Jul 27 at 16:34












up vote
1
down vote













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 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 at 11:57














up vote
1
down vote













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 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 at 11:57












up vote
1
down vote










up vote
1
down vote









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 Jul 28 at 14:55


























answered Jul 28 at 0:59









slm♦

232k65479649




232k65479649











  • 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 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 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 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 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 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 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 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 at 11:57












 

draft saved


draft discarded


























 


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
































































-

Popular posts from this blog

How to check contact read email or not when send email to Individual?

Image
Clash Royale CLAN TAG #URR8PPP up vote 1 down vote favorite I'm using WordPress 4.9.8, CiviCRM to 5.5.1, I usually send email to contact by Search> Find contacts View contact details Action> Send email Send email ok, Contact received mail ok like picture But status only Email sent though contact read email or not. So, can CiviCRM can change status to Email read when contact read email? wordpress email share | improve this question asked Sep 26 at 0:12 ToanLuong 49 9 add a comment  |  up vote 1 down vote favorite I'm using WordPress 4.9.8, CiviCRM to 5.5.1, I usually send email to contact by Search> Find contacts View contact details Action> Send email Send email ok, Contact received mail ok like picture But status only Email sent though contact read email or not. So, can CiviCRM can change status to Email read when contact read email? wordpress email share | improve this questi...
Read more

Displaying single band from multi-band raster using QGIS

Image
Clash Royale CLAN TAG #URR8PPP 1 How can I extract a single band from multi-band raster in QGIS? I have an remote sensed image which has 6 bands (including NDVI band), I want to display each band separately, but have no idea how to do. I have seen some questions similar here but none worked for me. The original image (has 6 bands) is: I want to display the band 6 which should be like this: But I tried gdal_translate, and couldn't get the correct result. What I have got is: qgis raster multi-band share | improve this question edited Mar 5 at 0:53 Summer asked Mar 4 at 6:42 Summer Summer 23 6 Is this any help gis.stackexchange.com/questions/220658/… ? if not gis.stackexchange.com/questions/62133/… might help. – Michael Stimson Mar 4 at 6:46 Thanks for answering but when I used gdal_translate, qgis showed that 'Error 4: Kayena.tif: No such file or directory". Would you know how to fi...
Read more

How many registers does an x86_64 CPU actually have?

Image
Clash Royale CLAN TAG #URR8PPP up vote 2 down vote favorite I am currently learning reverse engineering and am studying the flags register. I had in my mind that rflags was just another name for one of the 16 general purpose registers, for example rax or rbx . But it looks like rflags is actually an additional register. So that makes 17 registers in total... how many more could there be? I have spent at least an hour on this and found numerous different answers. The best answer so far is this, which says that there are 40 registers in total. 16 General Purpose Registers 2 Status Registers 6 Code Segment Registers 16 SSE Registers 8 FPU/MMX Registers But if I add that up, I get 48. Could anybody provide an official answer on how many registers an x86_64 CPU has (e.g. an Intel i7). Additionally, I have seen references to 'hardware' and 'architectural' registers. What are those registers and how many are there? register x86-64 share | improve this...
Read more