Does anyone know how to fix the following error after running

make pull-openlane

?

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

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?

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?

What does

python3 ./dependencies/get_tag.py

give you?

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.

Looks like a problem with the

get_tag.py

script. Do you want to log an issue? Line 56 is

["git", "rev-parse", "HEAD"],

but should maybe be

["git", "tag", "--list", "--contains", "HEAD"],

You should be able to workaround it by executing

export OPENLANE_DOCKER_TAG=`git tag --list --contains HEAD`

before

make pull-openlane

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

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?

No disadvantages, just might take a bit longer.

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.

Precisely. Personally, I'm more a

make openlane

fan. That one always works.

Awesome! I'll do the same then, since I know about it now. Thanks a lot Donn!

Thanks for the update, @User!