Skip to content

vagrant snapshot restore - should not provision #6752

Closed
@jstortz

Description

I currently have two issues with the snapshot restore functionality. They may both be simple lack of education, improper workflow, etc., I don't know. I'm looking, but cannot find the answers so far.

The Setup

  1. I setup my Vagrantfile, including provisioning to get my machine close to how I need it
  2. I vagrant up
  3. I make final manual adjustments to get things "just so"
  4. I shut the machine down with vagrant halt machineName
  5. I use vagrant snapshot save machineName snapshotName and that works great too.

Expectations

When I use vagrant snapshot restore machineName snapshotName there are two things that happen that I did not expect/want:

  1. The machine actually boots up. I don't want it to that. I want it to restore and then await further use. I had previously taken the snapshot in a halted state. I expect the restore of the snapshot to put the machine back to the same state it was in when I took the snapshot (a.k.a., halted).
  2. Provisioning occurs. I tried adding --no-provision, but that didn't seem to help. The snapshot is exactly how I wanted the machine. The provisioning happened earlier when I did my original vagrant up. I don' want provisioning to occur again.

So I expect I may have different/unusual expectations or lack knowledge of a command line switch to use etc. Anyway, let he debate begin.

Thanks,
Jason

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions