Closed VishnuEaswaran closed 3 years ago
I expected something like this to popup. Actually the .so
files are not meant to be in the repo but are still
needed for some hacky build scripts. I have amended .gitignore
to include libSockPipes.so file in the repo,
please pull the latest commit and try it again.
PS: What is meant by a 'shallow' clone of marshal?
Okay, that sounds like the culprit.
Shallow clone is just cloning the repo without all the history. In my case I choose the "depth" as 1, which is the number of commits and related data to fetch from the current head, and selectively cloned just the marshal branch. Shallow cloning comes very handy when the repo is huge along with the history.
I am hoping that the docker setup went well. Hence closing the issue.
Thanks for sharing information on shallow clone. I had never used it before.
I haven't touched the repo this whole week. Will update this first thing tomorrow.
It seems some part of the bug still persist. I cloned the branch again today, removed all the prebuilt images and stages, then tried building but still encountered errors. The good news is that the base and build images are built successfully while the build_tools is failing. I am attaching the log and screenshot of docker images
UPDATE: Today I ran the script and it ran without issues. I will try once again and report here later; I hope the issue is resolved.
weirdly the very first run fail to build ajit_tools but the subsequent execution succeed. I don't know how to pin down what is wrong. Help needed.
I will try to do a fresh build and see if I can reproduce the issue.
I am getting a new error this time when I rebuild everything for my fresh OS install (Xubuntu 20.04). I couldn't find the mentioned script in ajit_build image too
I have fixed it. However, you shouldn't be getting this error unless the line with exit;
in the docker_setup.sh
is commented out.
Right now my efforts are focused on ajit_build_dev with is getting built successfully as printed in your logs.
I have made more improvements to the image and building process with some finer adjustments to
the user permissions etc. Please use the next commit where I will mention this issue.
Thank you @adhuliya. Yes this error occur while building ajit_tools. I will pull the commits and use hem in future,
@VishnuEaswaran The issues raised here are quite helpful to make the tool-chain robust. Thanks for the prompt support and communication.
The docker build is failing. Out of three images, only _ajitbase is getting built. I tried the build in a fresh, shallow clone of marshal and here is the log.
docker_build.zip
here is my
docker images
output