I need an advice for a trouble with "cf ic create volume" in bluemix for a days. I want to know the cause of the failure, whether bluemix's issue or issues in my setup procedure.
The command and response in the Docker Quickstart Terminal on Windows Server 2012R2:
$ cf ic create volume testvol
Error response from daemon:
{
"incident_id": "1455-1484451778.065-3843854",
"code": "IC5051E",
"description": "The image volume could not be retrieved. Verify that the image ID or name is correct.",
"environment": "prod-dal09",
"rc": "404",
"host_id": "177",
"type": "Infrastructure",
"name": "ImageNotFound"
}
FAILED
Command failed
Incident report on bluemix:
RESOLVED: Issues creating container volumes in US South and United Kingdom regions
Users are experiencing issues creating new file shares within the IBM Bluemix Container Service. Because of this, new volume creation is also affected. The engineering teams are working to restore service.
UPDATE 2017-01-13 22:10 UTC: the issue has been solved.
Updated: Jan 14, 2017 12:05 AM UTC+0000
Starts: Jan 9, 2017 6:59 PM UTC+0000
Ends: Jan 13, 2017 10:10 PM UTC+0000
Category: IBM Containers
Region(s): us-south
eu-gb
ID: 296975
My region is us-south. It looks resolved though my command still failed.
My environment is:
cf version 6.22.2+a95e24c-2016-10-27
IBM-Containers 0.8.964 ic IBM Containers plug-in
docker version Client:
Version: 1.12.5
API version: 1.24
Go version: go1.6.4
Git commit: 7392c3b
Built: Fri Dec 16 06:14:34 2016
OS/Arch: windows/amd64
docker version Server:
Version: 1.12.6
API version: 1.24
Go version: go1.6.4
Git commit: 78d1802
OS:Windows server 2012R2 on VMWare Workstation 12 Pro
You are typing the wrong command to create the volume.
The correct command to create a volume is:
$ cf ic volume create VOLUME_NAME
cf ic create will try to create a new container and it is expecting that volume is the image name, hence the error you are seeing.
You can see complete docs in the link below:
https://console.ng.bluemix.net/docs/containers/container_cli_cfic.html#container_cli_reference_cfic__d1430e3797
Related
I am trying to implement the BYFN Hyperledger example form my Windows 10 Linux Subsystem (Ubuntu Xenial). However, the ./byfn.sh -m up command fails with the following output:
$GOPATH/fabric-samples/first-network$ ./byfn.sh -m up
Starting with channel 'mychannel' and CLI timeout of '10' seconds and CLI delay of '3' seconds
Continue? [Y/n] y
proceeding ...
2018-04-24 22:12:44.343 UTC [main] main -> INFO 001 Exiting.....
LOCAL_VERSION=1.1.0
DOCKER_IMAGE_VERSION=1.1.0
Creating peer0.org1.example.com ... done
Creating orderer.example.com ... done
Creating peer1.org1.example.com ... done
Creating peer0.org2.example.com ... done
Creating peer1.org2.example.com ... done
Creating cli ... done
OCI runtime exec failed: exec failed: container_linux.go:348: starting container process caused "exec: \"scripts/script.sh\": stat scripts/script.sh: no such file or directory": unknown
ERROR !!!! Test failed
I see that only one container is built:
$GOPATH/fabric-samples/first-network$ dps
CONTAINER ID NAMES NETWORKS STATUS SIZE
3e66d31c6b9a cli net_byfn Up 27 minutes 17B (virtual 1.46GB)
From the output it seems that the cli container cannot see the script.sh script. Thinking this maybe a docker-compose volume-bind issue I tried to check the binds in the cli container:
$GOPATH/fabric-samples/first-network$ docker exec -ti cli bash
root#3e66d31c6b9a:/opt/gopath/src/github.com/hyperledger/fabric/peer# ls scripts/
root#3e66d31c6b9a:/opt/gopath/src/github.com/hyperledger/fabric/peer# exit
exit
$GOPATH/fabric-samples/first-network$ ls scripts/
capabilities.json script.sh step1org3.sh step2org3.sh step3org3.sh testorg3.sh upgrade_to_v11.sh utils.sh
Looking at the the docker-compose-cli.yaml file I see the following binds for the cli container:
volumes:
- /var/run/:/host/var/run/
- ./../chaincode/:/opt/gopath/src/github.com/chaincode
- ./crypto-config:/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/
- ./scripts:/opt/gopath/src/github.com/hyperledger/fabric/peer/scripts/
- ./channel-artifacts:/opt/gopath/src/github.com/hyperledger/fabric/peer/channel-artifacts
My Docker settings:
$GOPATH/fabric-samples/first-network$ docker version
Client:
Version: 18.03.0-ce
API version: 1.37
Go version: go1.9.2
Git commit: 0520e24
Built: Wed Mar 21 23:05:52 2018
OS/Arch: linux/amd64
Experimental: false
Orchestrator: swarm
Server:
Engine:
Version: 18.03.0-ce
API version: 1.37 (minimum version 1.12)
Go version: go1.9.4
Git commit: 0520e24
Built: Wed Mar 21 23:14:32 2018
OS/Arch: linux/amd64
Experimental: false
$GOPATH/fabric-samples/first-network$ docker-compose version
docker-compose version 1.21.0, build 5920eb0
docker-py version: 3.2.1
CPython version: 3.6.5
OpenSSL version: OpenSSL 1.0.1t 3 May 2016
My Go version:
$GOPATH/fabric-samples/first-network$ go version
go version go1.10.1 linux/amd64
Wondering if I'm missing something. I should mention that I used the following command to start form scratch, based on a fresh set of images (no prior images) as outlined in this script:
curl -sSL https://raw.githubusercontent.com/hyperledger/fabric/master/scripts/bootstrap.sh | bash -s 1.1.0
Thanks
Its most probably the version of golang---Fabric needs go version 1.9.x and the error message exec failed: container_linux.go:348: indicates the same thing.
In my case, it was the first Note on this page https://hyperledger-fabric.readthedocs.io/en/latest/install.html
I'm running on Windows 10, but Docker won't work since i need Windows 10 Pro or better to run it. So i'm using Docker Toolbox, and must follow the Windows 7 trick of cloning the sources anywhere under C:\Users
I install pgadmin 4 from apt and latest postgres 10 from Docker. And I can't create database. When I try to create it I get error "Error saving properties. Click for details"
Version2.1
CopyrightCopyright 2013 - 2018, The pgAdmin Development Team
Python Version3.5.2 (default, Nov 23 2017, 16:37:01) [GCC 5.4.0 20160609]
Flask Version0.10.1
Application ModeDesktop
Current Userpgadmin4#pgadmin.org
I have deployed a 4 node Couchbase cluster using Google GKE.
The master node exposes ports 8091, 8093 to the Loadbaancer.
When connecting to the Loadbalancer IP (external) via a Java app to insert data, I get the timeout error with this stack:
Apr 04, 2017 3:32:15 PM com.couchbase.client.core.endpoint.AbstractEndpoint$2 operationComplete
WARNING: [null][ViewEndpoint]: Socket connect took longer than specified timeout.
Apr 04, 2017 3:32:15 PM com.couchbase.client.core.endpoint.AbstractEndpoint$2 operationComplete
WARNING: [null][KeyValueEndpoint]: Socket connect took longer than specified timeout.
Apr 04, 2017 3:32:15 PM com.couchbase.client.deps.io.netty.util.concurrent.DefaultPromise notifyListener0
WARNING: An exception was thrown by com.couchbase.client.core.endpoint.AbstractEndpoint$2.operationComplete()
rx.exceptions.OnErrorNotImplementedException: connection timed out: /10.4.0.3:8093
at rx.Observable$26.onError(Observable.java:7955)
at rx.observers.SafeSubscriber._onError(SafeSubscriber.java:159)
at rx.observers.SafeSubscriber.onError(SafeSubscriber.java:120)
at rx.internal.operators.OperatorMap$1.onError(OperatorMap.java:48)
What's puzzling is that the stack shows 10.4.0.3:8093 which is actually the the IP of the docker container.
Appreciate all suggestions.
Have you checked the firewall rules for the master node and the workers? You need to allow ingress for the ports you have set up.
See this answer
The main goal is to run the ServiceBus in a docker container for windows.
Output of docker version:
Client:
Version: 1.13.1
API version: 1.26
Go version: go1.7.5
Git commit: 092cba3
Built: Wed Feb 8 08:47:51 2017
OS/Arch: windows/amd64
Server:
Version: 1.13.1
API version: 1.26 (minimum version 1.24)
Go version: go1.7.5
Git commit: 092cba3
Built: Wed Feb 8 08:47:51 2017
OS/Arch: windows/amd64
Experimental: true
Dockerfile content:
# Is used as sql server local storage for servicebus
FROM microsoft/mssql-server-windows-express
COPY install/ /install
# WebPlatform Installer http://download.microsoft.com/download/C/F/F/CFF3A0B8-99D4-41A2-AE1A-496C08BEB904/WebPlatformInstaller_amd64_en-US.msi
RUN msiexec /i install\WebPlatformInstaller_amd64_en-US.msi /qn
# Install servicebus using webpicmd offline installation https://msdn.microsoft.com/en-us/library/dn441408.aspx#BMK_SBConfig1616
RUN WebpiCmd /Install /Products:ServiceBus_1_1 /AcceptEula /SuppressReboot /xml:c:\install\SBWebPICache\feeds\latest\webproductlist.xml
Steps to reproduce:
1. Build image with parameters:
docker build --no-cache -t servicebus $folder
...
Verifying successful installation...
Microsoft Visual C++ 2012 SP1 Redistributable Package (x64) True
Microsoft Windows Fabric V1 RTM True
Microsoft Windows Fabric V1 CU1 True
Windows Azure Pack: Service Bus 1.1 True
Windows Azure Pack: Update for Service Bus 1.1 - .NET Framework 4.6 Compatibility (KB3086798) True
Install of Products: SUCCESS
Servicebus installed successfully as expected
2. Run container with parameters:
docker run -it --rm --isolation hyperv servicebus powershell
3. Create new servicebus farm:
New-SBFarm -SBFarmDBConnectionString 'data source=.; integrated security=true' -CertificateAutoGenerationKey (ConvertTo-SecureString -string "P#assword" -force -AsPlainText)
Failed with error:
New-SBFarm : The Server service is not started.
Starting service manually:
Start-Service : Service 'Server (LanmanServer)' cannot be started due to the following error: Cannot start service LanmanServer on computer '.'
Found that service depends on ‘srvnet’ that fails to start on Windows 10 (10.0.14393) using hyper-v isolation:
Start-Service : Failed to start service 'srvnet (srvnet)'.
But successfully starts on Windows Server 2016 (10.0.14393) using process isolation. However, even with srvnet service running and File-Services installed it's still not working. Server lanmanserver service can not be started
Question:
Are any possibilities to make lanmanserver working inside windows container? Or any other ways to create servicebus farm?
On September I received an email saying that the old stack (lucid64) will be removed by the end of October.
The email also said that on Oct 17 (three days ago) Bluemix will initiate an automatic migration to cflinuxfs2.
How do I know if my app was already migrated?
Do I have to run cf push with the -s cflinuxfs2 flag from now on? If yes, until when?
I have executed cf push several times this month but without the -s flag.
Thanks
cf app APP_NAME should show you the stack, e.g.:
$ cf app APP_NAME
Showing health and status for app APP_NAME in org ORG_NAME / space SPACE_NAME as ME#MY_DOMAIN.com...
OK
requested state: started
instances: 2/2
usage: 32M x 2 instances
urls: APP_NAME.APP_DOMAIN.com
last uploaded: Mon Oct 19 02:21:39 UTC 2015
stack: cflinuxfs2
buildpack: go_buildpack
state since cpu memory disk details
#0 running 2015-10-18 07:22:08 PM 2.1% 10.7M of 32M 38.9M of 64M
#1 running 2015-10-18 07:22:07 PM 2.1% 8.4M of 32M 38.9M of 64M
You can see it says stack: cflinuxfs2
Running the following command will show you your application stack.
[07:40:10 ~]$ cf app velocityapp
...
stack: cflinuxfs2
You can re-push your application with the -s flag or the platform will automatically migrate you at a later date.