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

Fix Vagrant so that it uses new CLI #117

Closed
Almansherov opened this issue Aug 29, 2018 · 2 comments
Closed

Fix Vagrant so that it uses new CLI #117

Almansherov opened this issue Aug 29, 2018 · 2 comments
Assignees

Comments

@Almansherov
Copy link
Member

We will be able to avoid this message during the installation:

image

For more info:
https://optdyn.slack.com/archives/C93MLLTL4/p1535521197000100

@Almansherov
Copy link
Member Author

Used the commands: vagrant init subutai/stretch-master
Vagrant used the new CLI and has got me a new versions of vagrant plugin and box:

image

Issue is fixed on master

@kurmanbekova6
Copy link

Tested in prod
screenshot from 2018-11-14 15-50-19

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

3 participants