pri-m (principal manager) yarn error after running docker-compose up --build in Infrastructure

Running the infrastructure docker file using command:

docker-compose up --build with deployment/ci/Dockerfile. I am getting the below error on the pri-m stage of project building.

Please help me to understand the issue? And how can I solve it?
Also, let me know in case any other requirements need to meet.

Hi @sovrgn, Can you please help me here?

By Nishant Madan on 2022-11-13T23:50:05 (imported from GitLab)

Hi @nmadan , this is the first time I see this issue. Can you give me any clues on how to reproduce it? I will try to find why it might be doing this.

By Boyan Tsolov on 2022-11-15T08:52:49 (imported from GitLab)

To start with the OCM project.

The step by step would be:

git clone [infrastructure] cd infrastructure ./setup-gaia-x.sh --- (replicates the project structure and pulls the main branch on all projects) after 3. is successful run docker-compose up --build to build and launch (I changed the development to Ci Dockerfile.

Then I got this error.

By Nishant Madan on 2022-11-15T09:19:45 (imported from GitLab)

I can't seem to reproduce it. For now I can suggest, so it doesn't block you, that you can comment it out of the docker-compose (unless you specifically need an interface between OIDC and anoncreds). The principal manager maps the user info that comes from an OIDC token to a verifiable credential in the form of anoncreds.

By Boyan Tsolov on 2022-11-15T10:59:18 (imported from GitLab)

@sovrgn I want to tell you about the situation I'm facing. With dev/Dockerfile it is working fine but I'm getting the Postgres table/schema error which is but obvious that we're building the project for the first time and the tables are not present.

Nevertheless, when I changed the docker compose file with ci/Dockerfile. I'm getting the exact same error which I've shared with me. So, I'm doing nothing special just trying to run the OCM project on my local.

Please do let me know what to do in such scenario? Because I've already gone through all the solutions that you've suggested in the other issues and, I am following the exact same steps that you've suggested.

By Nishant Madan on 2022-11-15T14:18:10 (imported from GitLab)

The issue looks like deprecated types inside of the prisma package, so...

Can you confirm in the package.json that the following packages match:

...
"@prisma/client": "^3.9.2",
...,
"pg": "^8.7.3",
"prisma": "^3.9.2",
...

By Boyan Tsolov on 2022-11-15T14:34:12 (imported from GitLab)

I can confirm that it is the updated code and all is present there.

By Nishant Madan on 2022-11-16T13:10:39 (imported from GitLab)

@sovrgn Please let me know in case anything else is required from my side.

By Nishant Madan on 2022-11-16T13:46:09 (imported from GitLab)

changed iteration to GXFS OCM E1 Sprints Nov 13, 2023 - Nov 26, 2023

removed iteration GXFS OCM E1 Sprints Nov 13, 2023 - Nov 26, 2023

changed iteration to GXFS OCM E1 Sprints Nov 27, 2023 - Dec 10, 2023

closed