liip / liip/drifter

Make `vagrant up` work even if network is unavailable

Open
#226 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area: core type: feature
Dominant language
HTML
Stars
57
Forks
25
PR merge metrics
No merged PRs in 30d

Description

At the moment running `vagrant up` even on a box that is already provisioned on a computer that doesn't have any network access will result in an error because Vagrant cannot check for box updates.

We could add the following configuration option to the `Vagrantfile` to prevent box update checking: `config.vm.box_check_update = false`. It would be of course better that Vagrant doesn't completely fail but just warns about not being able to check for updates, but that's apparently not possible.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start in the Vagrantfile and review the existing VM configuration. Test `vagrant up` with the box already provisioned and network access unavailable. Done means the update check is disabled and the command no longer fails in that offline scenario.

Written by the indexing model from the issue text.

Assessment

Domain
devops
Issue type
Bug
Difficulty
1/5
Estimated time
Under an hour
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.