I'm running a composer install after a docker-compose up and am unable to get the CI process to continue. All of the output shows the install was successful except for travis' interpretation of the output. See https://travis-ci.org/BibleBowl/account/builds/125161543#L1454
Is there something I can do to show more verbose output?
Related
I am currently trying to set up some system testing for my rails web application (using Rails version 7.0.3.1)
When running rails test:system to run a single system test I had written, I am getting the below setup-related error
Command '/usr/bin/chromium-browser' requires the chromium snap to be installed.
Please install it with:
snap install chromium
.rbenv/versions/3.1.2/lib/ruby/gems/3.1.0/gems/webdrivers-5.0.0/lib/webdrivers/system.rb:190:in `call': Failed to make system call: ["/usr/bin/chromium-browser", "--product-version"] (RuntimeError)
And then, when I try to run
snap install chromium
as suggested by the error I am getting back, I then run into the following error
error: cannot communicate with server: Post http://localhost/v2/snaps/chromium: dial unix /run/snapd.socket: connect: no such file or directory
I am lost as to how to move forward with this issue, which is preventing me from being able to run any system tests. There also seem to not be too many related issues online currently that applied to this case. Any help/ suggestions on where to look to further troubleshoot this error would be greatly appreciated.
Try to install it from the Google, depends on your ubuntu versions:
wget https://dl.google.com/linux/direct/google-chrome-stable_current_amd64.deb
apt install ./google-chrome-stable_current_amd64.deb
I have a strange problem with podman. I have a large Dockerfile of an open source project called spilo that I was always able to build. Today for some strange reason the same code doesn't work anymore. It's true that I haven't used podman for a month but today I got a strange problem. To simplify the error I created a simple Dockerfile just to show you the problem:
ARG BASE_IMAGE=ubuntu:18.04
ARG PGVERSION=14
ARG COMPRESS=false
FROM $BASE_IMAGE as builder-false
RUN apt-get update; apt-get install -y pgbackrest
FROM scratch as builder-true
COPY --from=builder-false / /
FROM builder-${COMPRESS}
Now if I run:
podman build . -t prova:latest
I got the following error:
[3/3] STEP 1/1: FROM builder-false
Resolving "builder-false" using unqualified-search registries (/etc/containers/registries.conf.d/999-podman-machine.conf)
Trying to pull docker.io/library/builder-false:latest...
Error: error creating build container: initializing source docker://builder-false:latest: reading manifest latest in docker.io/library/builder-false: errors:
denied: requested access to the resource is denied
unauthorized: authentication required
It seems it try to search the builder-false image from docker.io repository instead try to build it from the row above. The steps to create the builder-false are not executed.
Can anyone help me to address this issue?
The original spilo project Dockerfile always worked. I reinstalled the podman VM but no luck. I also restarted the Mac, no luck.
I think there is a bug somewhere in dependencies of pgbackrest. I got this on my podman (centos 8) executing RUN apt-get install -y pgbackrest:
chfn: PAM: System error
adduser: `/usr/bin/chfn -f PostgreSQL administrator postgres' returned error code 1. Exiting.
dpkg: error processing package postgresql-common (--configure):
installed postgresql-common package post-installation script subprocess returned error exit status 1
With docker works fine.
I've been trying to run a development environment of the following SQL language server for VS Code. In the README, it says to use docker-compose up to initiate the docker container. However, every time I execute this command, I receive this error:
error An unexpected error occurred: "https://registry.yarnpkg.com/colors/-/colors-1.4.0.tgz: ETIMEDOUT"
I did research on issues with fetching Yarn packages, and the most prominent solution involved increasing the maximum timeout to 100000, and I did so with the following command:
yarn add colors/-/colors-1.4.0.tgz --network-timeout 100000 -W
This executes successfully, but I still receive the exact same error when I run docker-compose up. Another solution I found included manually downloading the package, and including a new COPY statement in the dockerfile with the location details (ex: COPY ./docker/colors-1.4.0.tar /opt/sql-language-server/docker), but this did nothing.
I'm trying to install syndesis on minishift following the official guides.
Installed minishift on ubuntu, no issues. Next I've tried
./syndesis minishift --install. In the end it says I have to run local dev builds for sysdesis-server syndesis-ui, etc
./syndesis build --app-images but got some dependency errors
Run syndesis quickstart. All the pods are up except syndesis-server. It doesn't start due to error like UnknownHostException: syndesis-db in the migration bean
Also tried ./syndesis minishift --install --tag 1.8.12 to install stable version but not sure if I'm doing it right cause no success
Any help ?
Sorry for the late response. We moved to use an Operator to do the installation and it caused a bunch of installation issues. If you have minishift installed then on Linux or Mac you should be able to get Syndesis installed using
bash <(curl -sL https://syndes.is/start)
See also: https://github.com/syndesisio/syndesis-quickstarts/blob/master/README.md#3-install-syndesis
It uses the syndesis bash command line tool from (https://github.com/syndesisio/syndesis/blob/master/tools/bin/), so you can check out the code yourself too and run that using:
./.syndesis/bin/syndesis minishift --install --full-reset --nodev --open
and then you can explore other options to specify a tag if you want.
Hope this gets you going!
Cheers,
--Kurt
I am biginner in block chain development. I succesfully run ./startFabric.sh and ./createPeerAdminCard.sh .Then i succesfully run two command as follow below.
composer runtime install -c PeerAdmin#byfn-network-org1-only -n trade-network
composer runtime install -c PeerAdmin#byfn-network-org2-only -n trade-network
Then i tried to run
composer identity request -c PeerAdmin#byfn-network-org1-only -u admin -s adminpw -d alice
But i got error like the following
Error: failed to request identity. Error trying to enroll user and return certificates. Error: Calling enrollment endpoint failed with error [Error: connect ECONNREFUSED 127.0.0.1:7054]
I tried many time to kill all process in docker and remove .composer file from home directory. But always showing the same error message.
Please help me as possible
Os: Ubuntu 16.04
Fabric vertion:1.0.4
Composer vertion:0.16.6
Thanks..
This error "Failed to import the business network card Connection profile has no x-type property defined." means that a v0.20 client can't/won't import a card from an earlier version (probably v0.16).
I think maybe you are running the wrong version of createPeerAdminCard.sh script and it is trying to create and import an 'old' card.
With Composer v0.20 you need to get 'new' copies of the fabric-development-servers scripts which work with Fabric 1.2.
So I would suggest running the following:
run teardownAllDocker.sh script
remove the fabric-dev-server folder (might be fabric-tools if old)
remove the ~/.composer folder
follow the install doc from Step 4 . - make sure to export FABRIC_VERSION=hlfv12 - this is what makes sure you get Fabric 1.2.
This is difficult to help ...
The first 2 scripts you have run (./startFabric.sh and ./createPeerAdminCard.sh) are for a basic development Fabric.
The next 2 commands look like they are from the Multi-Org tutorial which uses a different Fabric and has different cards and crypto material.
Unless there is a particular reason for using an old version of Composer, I would suggest using Composer v0.20, which requires Fabric 1.2.
If you are a beginner I would suggest working with the Developer Tutorial to start with.
if you are using a default file (e.g. connection.json, env.json, etc.) to hold your base connnection profile, simply change the "type" term in that default file to "x-type"
In converting from v0.16 to v0.20, you must first remove the v0.16 composer tools from your system, then install the v0.20 version.
To remove v0.16.6:
npm uninstall -g composer-cli
npm uninstall -g generator-hyperledger-composer
npm uninstall -g composer-rest-server
To install V0.20.2:
npm install -g --python=python2.7 composer-cli#0.20.2
npm install -g --python=python2.7 generator-hyperledger-composer#0.20.2
npm install -g --python=python2.7 composer-rest-server#0.20.2
npm install -g --python=python2.7 yo
If you're running nodejs, then you also have to update both package.json files (network/package/json as well as your {base folder}package.json) from 0.16.x to ^0.20.2
The reason for error is Missing of Certificate Authorities(CA). I Just up my CA server. Now Working perfectly.