https://open-source-silicon.dev logo
#openlane
Title
# openlane
a

Anuj Dubey

03/14/2022, 3:53 AM
Does anyone know how to fix the following error after running
make pull-openlane
?
Copy code
Pulling most recent OpenLane image relative to your commit...
docker pull efabless/openlane:5f20beb7928c7329ea1a199b9f494f48f2e6c080
Error response from daemon: manifest for efabless/openlane:5f20beb7928c7329ea1a199b9f494f48f2e6c080 not found: manifest unknown: manifest unknown
Makefile:96: recipe for target 'pull-openlane' failed
make: *** [pull-openlane] Error 1
m

Mitch Bailey

03/14/2022, 5:18 AM
Have you set
OPENLANE_TAG
to something other than the default? Are you on
mpw-5c
or someother branch? What directory are you executing in? What is
OPENLANE_IMAGE_NAME
set to?
a

Anuj Dubey

03/14/2022, 8:21 AM
I have not set any of these variables. There is no mpw-5c; I am trying to build openlane as a standalone flow instead of it being used as part of the caravel flow. So I simply cloned the latest openlane repo and called make pull-openlane as the doc states. Should I set these variables to something prior to calling the make command? Based on the Makefile, I think it should automatically set these variables, no?
m

Mitch Bailey

03/14/2022, 8:26 AM
What does
python3 ./dependencies/get_tag.py
give you?
a

Anuj Dubey

03/14/2022, 12:30 PM
The latest commit hash. And then the tool tries to perform a docker pull efabless/openlane:<commit hash>. But turns out this image doesn't exist.
m

Mitch Bailey

03/14/2022, 1:14 PM
Looks like a problem with the
get_tag.py
script. Do you want to log an issue? Line 56 is
Copy code
["git", "rev-parse", "HEAD"],
but should maybe be
Copy code
["git", "tag", "--list", "--contains", "HEAD"],
You should be able to workaround it by executing
Copy code
export OPENLANE_DOCKER_TAG=`git tag --list --contains HEAD`
before
make pull-openlane
@User
d

donn

03/14/2022, 1:42 PM
@User @User There is a small period of time after an OpenLane repo is built, 30 minutes to 1 hour or so, where the tag's image has not yet been pushed to docker hub. This is unavoidable. You can
make openlane
if you can't wait for the CI process.
We've transitioned from tags to hashes for matching OpenLane commits with images. Tags are imprecise, I've found.
a

Anuj Dubey

03/14/2022, 1:53 PM
Hi Donn, I still can't seem to run make pull-openlane successfully. I've been intermittently trying over past couple of hours. So it has been certainly more than 30 min to 1 hour. What's the solution here if I indeed want to use the pull-openlane target? The vanilla openlane target works for now, as you've suggested--what's the disadvantage of this approach over the pull-openlane target build?
Also, thanks Mitch for debugging this for me! 🙂
d

donn

03/14/2022, 1:54 PM
No disadvantages, just might take a bit longer.
Also- there was an issue with this specific commit, apologies.
git pull && make pull-openlane
should work.
a

Anuj Dubey

03/14/2022, 1:56 PM
I see. Got it. So you're suggesting, in general, if I make the pull-openlane target and encounter the manifest error, it should go away in an hour or so—the time it takes to upload on the docker hub.
d

donn

03/14/2022, 1:57 PM
Precisely. Personally, I'm more a
make openlane
fan. That one always works.
a

Anuj Dubey

03/14/2022, 2:00 PM
Awesome! I'll do the same then, since I know about it now. Thanks a lot Donn!
m

Mitch Bailey

03/14/2022, 2:45 PM
Thanks for the update, @User!
👍 1
2 Views