‘make’ Errors about puma

[nachovizzo]

Do docker system prune -a and then try again ;)

[nachovizzo]

Sorry for the late reply. Apparently, the Kitware people changed a public key without previous notice. Meaning that the image is now broken. I will update the docker images and let you know in this issue when the process is ready

[nachovizzo]

Done!, please check now again if it's working and please let me know ;)

[qixuema]

First of all, thank you very much for your reply. After I update the code, i enter ‘make’ in the terminal again. It may be that I haven't configured it properly, which leads to the problem still exists . I feel a little confused about this.

[qixuema]

wow, it's cool! Thank you so much! it works well.

[qixuema]

I'm sorry, the problem about “NO_PUBKEY” has arisen again. I tried to use docker system prune -a and make it again, but it failed. Did the key update or something else go wrong?
I'm looking forward to your reply.

[nachovizzo]

This looks exactly like before. I just executed docker system prune -a and then make and it's working. The problem is that you still how somehow have an old image. I completely removed the custom version of cmake on 62a1837, meaning that if your docker image is trying to fetch the apt.kitware.com repo, is because you have an old image.

[qixuema]

Sorry for the late reply.
I tried to remove all unused containers and images, leaving only my commonly used QQ and wechat.
Then I pulled the latest code again and executed docker system prune -a, but the problem still appeared. Do I need to remove QQ and wechat?

[nachovizzo]

I'm not sure if that would help, I can also not reproduce the problem. Please try to build the apps container with this command docker-compose build --no-cache apps, on the root of the repository

[qixuema]

Sorry, I tried to execute the docker-compose build --no-cache apps command in the root directory, but the error still exists. Maybe my system is not set up or cleaned up. I'll think of another way. Thank you！