Pin golangci-lint version

[han-minhee]

This patch pins the version of golangci-lint
as the lastest version gives a parsing error

[han-minhee]

I'll amend the commits soon

[han-minhee]

I'm now working on enabling the Docker tests to run without errors

[han-minhee]

@artek-koltun I'm not sure what's causing the docker test to fail. Could you look into the issue? It works on my local environment.

[artek-koltun]

@artek-koltun I'm not sure what's causing the docker test to fail. Could you look into the issue? It works on my local environment.

ok, let's try to troubleshoot it. It says

No such image: opi-mangoboost-bridge-opi-mangoboost-server:latest

and I do not see that it even tried to build the image...
If you run locally what is the name of your image locally? opi-mangoboost-bridge-opi-mangoboost-server or maybe opi-mangoboost-bridge_opi-mangoboost-server?

[han-minhee]

It's opi-mangoboost-bridge-opi-mangoboost-server,

I realized I should run SPDK separately before running opi-test, which isn't included in the docker-compose.
Should I include spdk in my docker-compose to pass the test?
I see no spdk included in intel's docker-compose file.

REPOSITORY                                    TAG                IMAGE ID       CREATED         SIZE
opi-mangoboost-bridge-opi-mangoboost-server   latest             5e620b69b6be   5 minutes ago   69.7MB

The containers during docker compose command:

 ✔ opi-mangoboost-server                                    Built       
 ✔ Network opi-mangoboost-bridge_opi                        Created     
 ✔ Container opi-mangoboost-bridge-jaeger-1                 Healthy     
 ✔ Container opi-mangoboost-bridge-redis-1                  Healthy     
 ✔ Container opi-mangoboost-bridge-opi-mangoboost-server-1  Healthy     
 ✔ Container opi-mangoboost-bridge-opi-gw-test-1            Exited      
 ✔ Container opi-mangoboost-bridge-opi-jaeger-test-1        Exited      
 ✔ Container opi-mangoboost-bridge-opi-test-1               Started

[artek-koltun]

It's opi-mangoboost-bridge-opi-mangoboost-server,

I realized I should run SPDK separately before running opi-test, which isn't included in the docker-compose. Should I include spdk in my docker-compose to pass the test? I see no spdk included in intel's docker-compose file.

REPOSITORY                                    TAG                IMAGE ID       CREATED         SIZE
opi-mangoboost-bridge-opi-mangoboost-server   latest             5e620b69b6be   5 minutes ago   69.7MB

The containers during docker compose command:

 ✔ opi-mangoboost-server                                    Built       
 ✔ Network opi-mangoboost-bridge_opi                        Created     
 ✔ Container opi-mangoboost-bridge-jaeger-1                 Healthy     
 ✔ Container opi-mangoboost-bridge-redis-1                  Healthy     
 ✔ Container opi-mangoboost-bridge-opi-mangoboost-server-1  Healthy     
 ✔ Container opi-mangoboost-bridge-opi-gw-test-1            Exited      
 ✔ Container opi-mangoboost-bridge-opi-jaeger-test-1        Exited      
 ✔ Container opi-mangoboost-bridge-opi-test-1               Started

No, you don't need to run spdk. Currently, docker-compose test just sends a list grpc request to the server and waits for response to make sure that the server is healthy.

The problem is that in the default version of docker compose 2.36.2, build is not performed. I will pin the version to 2.36.0 and get back to you

[sandersms]

I reviewed and merged the pinned docker compose version from @artek-koltun into the actions and requested the test to be re-run. It still is indicating the same error for the server functionality. I will take a look also and see if there is anything that I notice in the operation.

[artek-koltun]

Now, the job should contain Install Docker Compose v2.36.0 step, but I do not see it in the logs. @han-minhee can you pls try to force push? or open a new pr with the same change?

[han-minhee]

Now, the job should contain Install Docker Compose v2.36.0 step, but I do not see it in the logs. @han-minhee can you pls try to force push? or open a new pr with the same change?

I've force pushed the commit.

[artek-koltun]

Now, the job should contain Install Docker Compose v2.36.0 step, but I do not see it in the logs. @han-minhee can you pls try to force push? or open a new pr with the same change?

I've force pushed the commit.

thanks. The test passed: https://github.com/opiproject/opi-mangoboost-bridge/actions/runs/16134766675/job/45535400632

[han-minhee]

Thank you for your help, both of you!