Bug 1316236 - [CDK] vagrant-landrush plugin install failed on F23 [NEEDINFO]
Summary: [CDK] vagrant-landrush plugin install failed on F23
Keywords:
Status: NEW
Alias: None
Product: Container Development Kit (CDK)
Classification: Red Hat
Component: distribution
Version: ---
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
: ---
Assignee: Lalatendu Mohanty
QA Contact: David Kutálek
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-09 18:29 UTC by Frederic Hornain
Modified: 2023-07-21 23:14 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:
prkumar: needinfo? (fhornain)


Attachments (Terms of Use)

Description Frederic Hornain 2016-03-09 18:29:42 UTC
Description of problem:

I am not able to install the vagrant landrush plugins provided in the Container Development Kit : cdk-2.0.0-beta4 on F23.

Indeed, I followed the steps described in the official documentation  :

https://access.redhat.com/documentation/en/red-hat-enterprise-linux-atomic-host/version-7/container-development-kit-installation-guide/#troubleshooting_problems_with_the_cdk_2

Here is the ouput of the command line :

$ vagrant plugin install vagrant-landrush
Installing the 'vagrant-landrush' plugin. This can take a few minutes...
Bundler, the underlying system Vagrant uses to install plugins,
reported an error. The error is shown below. These errors are usually
caused by misconfigured plugin installations or transient network
issues. The error from Bundler is:

Could not find gem 'vagrant-landrush (>= 0) ruby' in the gems available on this machine.

Comment 1 Praveen Kumar 2016-03-29 08:58:04 UTC
@Frederic, With beta-5 we are not promoting 'landrush' instead using 'xip.io', Also documents link which you provided are updated with beta5 release and you don't have to install 'landrush' to play around with CDK boxes. 

Please try out latest release (beta5) and let us know if this is still a issue?


Note You need to log in before you can comment on or make changes to this bug.