project-eve / zenbuild

Linuxkit based IoT Edge Operating System (Zenix)
https://www.zededa.com
Apache License 2.0
14 stars 7 forks source link

Error in building zenbuild #76

Closed meetcarey closed 5 years ago

meetcarey commented 5 years ago

Getting the following error during 'make fallback.img'.

Digest: sha256:14dbb5f1e3b201799e2f63fc1173772946b48798cb0cbb78acad4d0d4b2a6c0b Status: Downloaded newer image for zededa/zisp:e8f5d2ad9fa4a0af649d9a2d8f3461c678d7c211 Building "zededa/zedctr:d509dfbe651aeb392ac6bb3f8e6e110362694e26" Error response from daemon: pull access denied for zededa/zedctr, repository does not exist or may require 'docker login' No image pulled, continuing with build Sending build context to Docker daemon 20.99kB Step 1/31 : FROM zededa/debug:3aeeaf4e04f450283d49220eb7e82262b4531687-amd64 as ztools ---> ed6c2d067d21 Step 2/31 : FROM scratch-amd64 as lisp pull access denied for scratch-amd64, repository does not exist or may require 'docker login' exit status 1 Makefile:17: recipe for target 'build' failed But Docker login was done before this, and was successful. It looks like this is trying to access a restricted docker image, where I am not given access?
eriknordmark commented 5 years ago

The lisp code was just open sourced last week, so we need to rework the build to work with that.

rvs commented 5 years ago

Hi @meetcarey There are two issues here -- as @eriknordmark pointed out -- now that the LISP is opensourced we can actually simplify this arcane portion of the build that deals with closed repos. That said, it still should've worked for you -- so thanks for reporting an issue. I'll look into how to fix the immediate problem tonight (while we add open sourced lisp to the build process)

meetcarey commented 5 years ago

Thanks @rvs and @eriknordmark; will look for your update.

rvs commented 5 years ago

@meetcarey I pushed a temporary fix that should be able to get you further. Can you please give this a try and let me know if I can close the issue?

meetcarey commented 5 years ago

@rvs Thanks for the fix. Build went through fine. You may please close this issue.