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

VMs are duplicated #186

Open
mikescott opened this issue Jul 12, 2020 · 5 comments
Open

VMs are duplicated #186

mikescott opened this issue Jul 12, 2020 · 5 comments

Comments

@mikescott
Copy link

Software

  • Vagrant 2.2.9
  • Virtualbox 6.1.10 r138449
  • Vagrant Manager 2.7.1
  • macOS Catalina 10.15.5

Steps to reproduce

  1. Have no Vagrant VMs on the host machine
  2. vagrant up in some project
  3. 'Refresh' in Vagrant Manager

Expected Results

  • The new VM should be listed once, and running (green)

Actual Results

  • The new VM is listed twice, showing as both running and not running (green and red)
@Greenek
Copy link

Greenek commented Oct 20, 2020

I have similar issue, but for some reason it applies only for some projects and the states of these pairs are the same (not like in the example above).

Zrzut ekranu 2020-10-20 o 10 48 51

vagrant global-status shows the list without duplicates.

❯ vagrant global-status        
id       name     provider   state   directory                                  
--------------------------------------------------------------------------------
74785b8  default  virtualbox saved   /Users/greenek/Sites/k******n
dce072c  default  virtualbox aborted /Users/greenek/Sites/i******i            
e721006  default  virtualbox running /Users/greenek/Sites/e********s
  • Vagrant 2.2.10
  • Vagrant Manager 2.7.1
  • VirtualBox 6.1.14 r140239
  • MacOS 10.15.7

@RawDawg
Copy link

RawDawg commented Nov 5, 2020

Same issue, MacOS 10.15.7, Vagrant 2.2.10, vmware Vagrant provider.

With "Use instance path as display name" checked, it shows my machines as:
• System/Data/Users/MyUsername/MyFolder/VMName
• /Users/MyUsername/MyFolder/VMName

@SRWieZ
Copy link

SRWieZ commented Dec 18, 2020

Same issue

  • MacOS Big Sur 11.1 (20C69)
  • Vagrant Manager 2.7.1
  • Vagrant 2.2.14

No duplicates on vagrant global-status.

As @RawDawg say's, directories differ.

@proustibat
Copy link

I think it comes from the symlinks: https://www.robotanz.com/purpletree/2019/11/06/macos-catalina-system-and-data-volumes-seen-as-one-makes-things-trickier-than-before/

@bizrad
Copy link

bizrad commented Mar 7, 2022

This issue appears to have gone away for me now.

  • MacOS Monterey 12.2.1
  • Vagrant manager 2.7.1
  • Vagrant 2.2.19
  • virtualbox 6.1.32

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants