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

‘make’ Errors #12

Closed
qixuema opened this issue Mar 29, 2022 · 10 comments
Closed

‘make’ Errors #12

qixuema opened this issue Mar 29, 2022 · 10 comments

Comments

@qixuema
Copy link

qixuema commented Mar 29, 2022

Thank you much for your great work!
And when I try to enter ‘make’ in the terminal, there was something happened as fellows. Can you help me find out what's wrong? I will appreciate it very much!Sincerely waiting for your reply!

20220330112623

@nachovizzo
Copy link
Collaborator

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
Copy link
Collaborator

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

@qixuema
Copy link
Author

qixuema commented Apr 7, 2022

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.
7f0aff68ff723e172f4a3fc09ddf51b

@nachovizzo
Copy link
Collaborator

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

@qixuema
Copy link
Author

qixuema commented Apr 7, 2022

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

@qixuema qixuema closed this as completed Apr 7, 2022
@qixuema qixuema reopened this May 11, 2022
@qixuema
Copy link
Author

qixuema commented May 11, 2022

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.
微信图片_20220511231003

@nachovizzo
Copy link
Collaborator

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
Copy link
Author

qixuema commented May 12, 2022

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?
微信图片_20220512094845
微信图片_20220512094902

@nachovizzo
Copy link
Collaborator

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
Copy link
Author

qixuema commented May 12, 2022

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!

@qixuema qixuema closed this as completed May 12, 2022
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

2 participants