Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Aries-Vcr is difficult to install and the startup scripts can be unstable #744

Open
ianco opened this issue Mar 10, 2023 · 6 comments
Open

Comments

@ianco
Copy link
Contributor

ianco commented Mar 10, 2023

See this thread on Discord: https://discord.com/channels/905194001349627914/1078522185834053632

There are four different repositories involved in an Aries-Vcr install - https://github.com/bcgov/von-network, https://github.com/bcgov/aries-vcr, https://github.com/bcgov/aries-vcr-client and https://github.com/bcgov/aries-vcr-issuer-controller - and the installation is fairly complicated.

The instructions in the various repositories haven't been updated in awhile (some changes have been made recently specifically for some errors that were found).

The startup for some of the docker containers - especially the issuer - is very dependant on timing between the containers, and is not reliable on slower machines.

@kthomas-digicat
Copy link

When I issue ./manage build under aries-vcr/docker, I get the following error
Building solr image ...
error: Unable to load docker config: json: cannot unmarshal string into Go value of type docker.dockerConfig
FATAL: Error response from daemon:

Any help would be appreciated. I am using macOS Ventura 13.3.1, Docker version 20.10.23

@WadeBarnes
Copy link
Member

Check your version of s2i. If you are using the latest it could be causing that issue. v1.3.1 is known to work.

@WadeBarnes
Copy link
Member

@amanji, Which version was it that you had issues with yesterday? Have you have a chance to test any of the versions above v1.3.1?

@amanji
Copy link
Contributor

amanji commented Apr 18, 2023

I had issues with s2i v1.3.6. I have not yet tested with the versions between v1.3.1 (which worked for me) and v1.3.6.

@kthomas-digicat
Copy link

Check your version of s2i. If you are using the latest it could be causing that issue. v1.3.1 is known to work.

Thanks a lot @WadeBarnes , it works with version 1.3.1 of s2i. Really appreciate your timely help

@amanji
Copy link
Contributor

amanji commented Apr 19, 2023

I tested s2i versions backward from latest and it looks like the last working version is v1.3.4.

So it looks like something changed in v1.3.5 onwards since versions past this fail early with the following error:

FATAL: Error response from daemon: 

All was tested on Ubuntu 22.04.1 LTS

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants