I encountered an problem when push application to bluemix.
When I used the following command:
bluemix app push cam-dev
It told me to define build stack:
The app is invalid: Must specify either a buildpack_url or an admin_buildpack_name
Then I use the following command to use stack cflinuxfs2:
bluemix app push cam-dev -s cflinuxfs2
It failed with following errors:
ERROR Unsupported stack
See https://docs.cloudfoundry.org/devguide/deploy-apps/stacks.html for more info
Failed to compile droplet: Failed to run all supply scripts: exit status 1
Then I see the cflinuxfs2 stack is no longer supported. The message tells me to update my app stack to cflinuxfs3 by pushing it again. I did it but it also failed with the following message:
FAILED
Stack cflinuxfs3 not found
I don't know what I can do to update it to cflinuxfs3. I used cf stacks and found there are only 2 available stacks:
lucid64 Ubuntu 10.04 on x86-64
cflinuxfs2 Ubuntu 14.04.2 trusty
This issue is caused by the bluemix has not yet upgrade to cflinuxfs3 but the build pack for cflinuxfs2 has been removed. I found a solution for it:
Add the following lines to manifest.yml:
buildpacks:
- https://github.com/cloudfoundry/nodejs-buildpack#v1.6.56
Or you can use following command:
bluemix app push cam-dev -b https://github.com/cloudfoundry/nodejs-buildpack#v1.6.56
Related
Followed instructions and installed Docker for the first time. Then I input everything in terminal as stated. Error on make up language=node
cannot write /var/folders/fw/44x2zkk9337ddrtbq5cp5w940000gn/T/tmph4o_dkt6 because server did not provide an image ID
ERROR: Service 'frontend' failed to build : Build failed
make: *** [up] Error 1
zsh: command not found: #
This looks like a Docker issue - See this thread here:
docker buildx install
The above command seemed to work for these folks.
I'm trying to build and deploy app using new feature heroku.yml https://blog.heroku.com/build-docker-images-heroku-yml
Build was successful but after pushed to registry I see error:
unsupported
=!= Build failed due to an error:
=!= push step: exit status 1
If this persists, please contact us at https://help.heroku.com/.
Source code of heroku.yml https://github.com/jincod/AspNetCoreDemoApp/blob/develop/heroku.yml
Heroku only supports Linux images.
You cannot use microsoft/dotnet:2.1-sdk-alpin, as that's a windows image.
I have already implemented my .bna file named "supply-chain-network" but I think that the problem isn't in the .bna, since I have tried with another .bna(the basic-sample-network in hyperledger composer playground) and the problem still persists.
Composer version: 0.19.2
Operating System: Ubuntu 16.04 running in VM
Steps:
download the fabric-dev-servers
./downloadFabric.sh
./startFabric.sh
./createPeerAdminCard.sh
exported the basic-sample-network from the playground (my-basic-sample.bna)
composer network install --card PeerAdmin#hlfv1 --archiveFile my-basic-sample.bna#
composer network start --networkName my-basic-sample --networkVersion 0.0.1 --networkAdmin admin --networkAdminEnrollSecret adminpw --card PeerAdmin#hlfv1 --file networkadmin.card
And I got the following error:
Starting business network definition. This may take a minute...
Error: Error trying to start business network. Error: No valid responses from any peers.
Response from attempted peer comms was an error: Error: 2 UNKNOWN: chaincode error (status: 500, message: cannot get package for chaincode (my-basic-sample:0.0.1))
I have checked and the name of the network and the version by issue the command:
composer archive list -a my-basic-sample.bna
And I got:
Listing Business Network Archive from my-basic-sample.bna
Identifier:my-basic-sample#0.2.4-deploy.0
Name:my-basic-sample
Version:0.2.4-deploy.0
Command succeeded
I have tried to issue composer network start with version 0.2.4 instead of 0.0.1 and I got the same error.
The log of the docker by typing:
docker logs peer0.org1.example.com
I got:
I have seen on https://github.com/hyperledger/composer/issues/3591#issuecomment-386718739 that this error is caused by an extra character when copy pasting the command from the hyperledger composer website. I have done what hi2rashid suggests(copy the command to a notepad and then copy to the command line) but I still got the same error.
Anybody know how to fix this ?
You are very close to getting this working ...
The composer archive list command has listed the version as "0.2.4-deploy.0" - although this doesn't look like a version "number" it is. Your network start command should include --networkVersion 0.2.4-deploy.0
This long version comes from Composer Playground autogenerating versions when the model is upgraded.
I am getting this error when the deploy to GAE (RoR) is finished:
latest: digest: sha256:fae8a83d8a4503b9ca284ecfb70da5faf1b66b015804396c2282fae7fc5e4669 size: 75429
DONE
-----------------------------------------------------------------------------------------------------------------------------------------
Updating service [default]...failed.
ERROR: (gcloud.preview.app.deploy) Error Response: [13] The system encountered a fatal error
I have no idea what happens.
I checked the logs, and last register is about the docker build:
17:13:24.410
DONE
{
metadata:
{…}
textPayload:
"DONE"
insertId:
"271f3953-7ca6-4282-960a-fcb35a2261a2-316"
log:
"cloudbuild"
}
The application is running in development and production enviroment whitout errors.
Rails : 4.2.6
Ruby: 2.3.1
GCloud SDK: 108.0.0
Someone knows how to fix it?
Very thanks!
Temporally solve:
Just add --docker-build=remote option to you gcloud preview app deploy command. (Remote builds are working normally)
To debug the command use --verbosity debug option.
EDIT:
Response from google support:
Engineering is aware of an issue with the platform that would cause these errors. They are currently working on deploying a fix.
When forking a heroku app, I get the message "Cisaurus copy service no longer available. Use Heroku Platform API instead." No gem by that title is installed. What is causing this? Full output below, using [myapp] in place of the sourceapp name, and [targetapp] in place of the forked copy name:
[myapp]$ heroku fork -a [myapp] [targetapp]
Creating fork [targetapp]... done
Copying slug... Failed to fork app [myapp] to [targetapp].
! WARNING: Potentially Destructive Action
! This command will destroy edmeasured-sandbox (including all add-ons).
! To proceed, type "[targetapp]" or re-run this command with --confirm
[targetapp]
> [targetapp]
Deleting [targetapp]... done
Original exception below:
! Cisaurus copy service no longer available. Use Heroku Platform API instead. See: https://devcenter.heroku.com/articles/platform-api-copying-slugs
[targetapp]$
The issue is being caused by using an old version of Heroku Toolbelt. Updating via https://toolbelt.heroku.com allows the command to run as intended.