cf -v
cf version 6.13.0-e68ce0f-2015-10-15T22:53:58+00:00
Plugin IBM-Containers v0.8.723 successfully installed.
cf ic login
Expect: login successfully
Actual: Cloud Foundry CLI version 6.11.2 or later is required for the IBM Containers plug-in. Upgrade your Cloud Foundry CLI installation to continue.
How could this happened? I have installed the latest cf...
UPDATED 26 October 2015 the latest version (0.8.763 or later) of the cf ic plugin supports the 6.13 version of cf.
Run cf ic update and you should see the commands you need to run to upgrade the plugin (varies by operating system). Or check the documentation.
Previous answer follows:
Currently (19 October 2015) the IBM-Containers plugin (version 0.8.723 or earlier) is not compatible with the 6.13.x version of cf. We're working on patching our plugin. Sorry about that.
In the meantime, you can install CF 6.12.4 and then install the IBM Containers plugin. Or use the ice tools
Related
hi need some help please, i try to install the node-red-contrib-db2-for-i package on node-red (i used node red as a service on ibm cloud) but it fail. i have this bug :Failed to install: node-red-contrib-db2-for-i.
That package is explicitly for connecting to IBM DB2 running on iSerise and need Node-RED to be running on iSerise hardware as well.
It will NOT run on a x64 Linux machine.
From the README for the node:
Prerequisites
If you use the latest package version (>=0.1.5) :
5733OPS is not used anymore (Deprecated). A prerequisite is to install
the Node.js iDB Connector idb-connector (done automatically when
installing this package if not already present) with Node.js (version
8 and later) using a yum install. This node has to run on Node.js /
Node-RED on IBM i (Native driver) but there will be soon an ODBC
alternative :)
As the gcloud components doc said, we can install some tools like: minikube, kubectl using the below command:
gcloud components install minikube
What's the difference between the tools(minikube, kubectl) installed by gcloud components install command and the original tools minikube?
Does gcloud sdk have any customization or restrictions on these tools?
Can I use the original minikube and kubectl(e.g. installed by brew install kubectl command) to replace the gcloud component tools?
As far as I know, the only difference is the package manager and how you installed the component. Cloud SDK pulls the external components based on the latest version of the SDK. As example, by updating to the latest SDK (as of now 315.0.0), you'll be able to install Minikube 1.14.0. Checking the version of this component will also display a commit version that you can check on the official repository.
If you need to work on a feature that is available on the latest version, then I suggest that you continue using Homebrew. However if not, and you want your components managed by Google, then installing it via Cloud SDK is also a good choice.
When i published Asp.Net Core 2.2 web app to IBM Cloud Foundry App, I got this error.
ERROR Unable to install dotnet-runtime: no match found for 2.2.x in [1.0.11 1.0.12 1.1.9 1.1.10 2.0.7 2.0.9 2.1.2 2.1.4 2.1.5]
Failed to compile droplet: Failed to run finalize script: exit status 12
Looks like there's no Cloud Foundry buildpack supporting the version of ASP.NET Core you are looking for.
Run this command to see the supported buildpacks
ibmcloud cf buildpacks
This is what I see on my machine when I run the above command
If you observe there are three dotnet-core buildpacks supporting version 2.1.
For buildpack support statement, refer this link
I'm getting emails from google that I should migrate my gae apps from python 2.7 to python 2.7.11. But I can't find any example how to do it. Do you know how it can be done?
I believe you're receiving communications about Python SSL Version 2.7 Shutdown and the necessary migration to SSL version 2.7.11. You'll find more information in the link above but basically the migration involves:
Updating to the latest Cloud SDK version via gcloud components update.
Updating the app.yaml for all versions of your application
Deploying your updated application
Attempting to install plugins from the Bluemix Plugin Repository using the latest cf client:
cf version 6.14.0+2654a47-2015-11-18
on both Mac OSX and Centos 7, I get the following error when attempting an install from the repo (the following are from the Centos machine):
[michael#oracle ~]$ cf install-plugin -r bluemix vpn
Attention: Plugins are binaries written by potentially untrusted authors. Install and use plugins at your own risk.
Do you want to install the plugin vpn? (y or n)> y
Looking up 'vpn' from repository 'bluemix'
9741777 bytes downloaded...
FAILED
Downloaded plugin binary's checksum does not match repo metadata
Downloading the binary plugin and attempting a local install, gives me:
cf install-plugin bluemix-admin-linux_x64
Attention: Plugins are binaries written by potentially untrusted authors. Install and use plugins at your own risk.
Do you want to install the plugin bluemix-admin-linux_x64? (y or n)> y
Installing plugin ./bluemix-admin-linux_x64...
FAILED
exit status 127
Further examination yields:
ldd bluemix-admin-linux_x64
./bluemix-admin-linux_x64: error while loading shared libraries: ./bluemix-admin-linux_x64: unsupported version 6773 of Verneed record
While this example is for the vpn plugin, all plugins besides IBM-Containers yield the same results on a remote install attempt (the checksum error) and some variation in examining the binary itself, for instance with active_deploy:
ldd active-deploy-linux-amd64-0.1.67
linux-vdso.so.1 => (0x00007ffc649d4000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00000036a0a00000)
libc.so.6 => /lib64/libc.so.6 (0x000000369fe00000)
/lib64/ld-linux-x86-64.so.2 (0x000000369fa00000)
I've not seen this with other community Cloud Foundry plugins so this phenomenon seems unique to how these plugins are being generated by IBM. Any suggestions or thoughts on how I could resolve this myself (a source repo that I could compile these myself, while unfortunate, would suffice at this point).
Tks,
Actually the official CLI for Bluemix is the cloud Foundry CLI as described on Bluemix doc pages
https://www.ng.bluemix.net/docs/cli/downloads.html
I think your errors are depending from your error in referring the plugin.
Checking the doc page for cf vpn plugin for Bluemix
https://www.ng.bluemix.net/docs/cli/plugins/vpn/index.html
you have to specify the plugin version you downloaded (and right for your own environment) and not only 'vpn'
For MS Windows OS:
cf install-plugin vpn_windows64.exe
For Apple MAC OS:
cf install-plugin vpn_mac_os_amd64
For Linux OS:
cf install-plugin vpn_linuxamd64
You could also configure bluemix plugin repository as cf repository and then install the plugins choosing it as source repository.
Use this container, it has cf and container plugin installed already:
https://hub.docker.com/r/reachlin/bluemix/