Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Package machines as plain VMs, not templates #225

Closed
legal90 opened this issue Nov 2, 2015 · 1 comment
Closed

Package machines as plain VMs, not templates #225

legal90 opened this issue Nov 2, 2015 · 1 comment
Assignees
Labels
Milestone

Comments

@legal90
Copy link
Collaborator

legal90 commented Nov 2, 2015

Our official boxes and all other boxes created by Packer already contains a plain VM image inside.

But vagrant package command clones VM to template prior to packaging to the box. Actually, there is no any significant reason for this. Templates are the same as "plain" VM images except they could not be configured and started.

However, it causes a problem when we try to create a linked clone from such box - It fails because it's not possible to snapshot a VM template (it is "read-only").

So, I've decided to use only plain VMs inside boxes:

  1. On Import action we should check the VM image type. If it is a template, then convert it to plain VM (it's extremely fast and should be done only once). This helps to keep backward compatibility - all previously created boxes will work fine.
  2. On Export action we should clone VM to the VM, not to template
@legal90 legal90 added the task label Nov 2, 2015
@legal90 legal90 self-assigned this Nov 2, 2015
@legal90 legal90 added this to the vagrant-1.8.0 milestone Nov 2, 2015
@legal90
Copy link
Collaborator Author

legal90 commented Nov 11, 2015

Implemented by #227

@legal90 legal90 closed this as completed Nov 11, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant