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

Docker builder, error: "Submodule 'CloudCompare' could not be updated." #147

Open
kxd195 opened this issue Dec 6, 2023 · 4 comments
Open

Comments

@kxd195
Copy link

kxd195 commented Dec 6, 2023

Trying to build the Docker image, but coming to this error:

Submodule path 'CloudCompare/plugins/core/Standard/qTreeIso': checked out '25a9ca397d9fe2c02afd2740cbbc82df747a2b8a'
fatal: failed to unpack tree object ad41baa8e4bbb8fcd599769400e2a3b04128352c
error: Submodule 'CloudCompare' could not be updated.
error: Cannot update submodule:
CloudCompare

Any clues why? Seems like it has more to do with the Git repo it's getting this submodule from.

@prascle
Copy link
Collaborator

prascle commented Dec 7, 2023

Hello,
I reproduce the bug. I don't check and update the docker script regularly, and something is broken in the git submodules repositories starting from the git tag used in the docker file.
If I replace the git tag CloudComPy_docker-20230216 by CloudComPy_master_2023_10_26 in Dockerfile_CloudComPy310_build, line 16, it's OK.

Regards,
Paul

@WolfRoyal
Copy link

Hello Paul,

I also have the same issue.
Last month (22.12.2023) your git tag changed worked for me when I replaced "CloudComPy_docker-20230216" with "CloudComPy_master_2023_10_26".
However, as of today I cannot create the docker image anymore and I am getting the "error: Cannot update submodule" error again.
Is there a new tag, I have to exchange it with?

Best,

Eric

@prascle
Copy link
Collaborator

prascle commented Jan 12, 2024

Hello Eric,
Sorry, my mistake... The chain of submodules is broken on my repository with the tag CloudComPy_master_2023_10_26
It works for me with the latest tag CloudComPy_master_2023_12_19.

Best,
Paul

@WolfRoyal
Copy link

Hello Paul,

no problem at all, thank you for your answer.
I now tested the suggested tag and everything works fine now :).
Thanks a lot!

Best,

Eric

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

3 participants