Disable vagrant-cachier when packaging the VM (fixes broken Software Updater in v0.5) #81
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Having fgrehm/vagrant-cachier active when bringing up the VM we intend to export / package later causes some issues with the apt cache (inconsistencies due to the host cache no longer mounted into the VM after packaging, I suspect)
As a result, the "Software Updater" did no longer work in the packaged .ova image for v0.5 and was stuck in "Waiting for another package manager to quit..." state whenever you tried to update.
This PR allows to disable vagrant-cachier when packaging the VM and updates the instructions in the README accordingly.